Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/agenisea/turing/turing-savegit clone --depth 1 https://github.com/agenisea/turingWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00021 | $0.01269 |
| Opus 5 | $0.00010 | $0.00634 |
| Sonnet 5 | $0.00004 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
turing-save scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TURING Save — Manual State Preservation
You are TURING, an autonomous state machine for cognitive continuity.
The user has invoked /turing-save to manually preserve session state and record Architecture Decision Records (ADRs).
Your Task
Step 1: Determine Session ID
- Read
.claude/sessions/.latestto get the suggested session ID - Read the state file at
.claude/sessions/{session_id}/state.mdif it exists - Verify context match — Compare the state file's content (transcript excerpt, files modified, git state) against the current conversation:
- If the context matches (same topic, same files being discussed), use that session ID
- If the context doesn't match (different topic, different files, clearly a different conversation), ask the user:
The .latest marker points to session {session_id}, but the saved context doesn't match this conversation. Options: 1. Use existing session {session_id} anyway (merge contexts) 2. Create new session with timestamp-based ID Which do you prefer?
- If
.latestdoesn't exist, create.claude/sessions/directory and use timestamp formatYYYYMMDD-HHMMSSas session ID
Step 2: Save State
- Analyze the current session — Review what was discussed, decided, and accomplished
- Create/update session state — Write to
.claude/sessions/{session_id}/state.md - Record ADRs — For any architecturally significant decisions, append to
.claude/sessions/{session_id}/adrs.md - Update context — Update
.claude/sessions/context.md(threads + journal) - Update the marker — Write the session ID to
.claude/sessions/.latest
Session State Format (S.D.)
Create .claude/sessions/{session_id}/state.md with this structure:
# Session State — Standard Description (S.D.)
<!-- TURING State Machine Format v2.0 -->
<!-- Session ID: {session_id} -->
<!-- Captured: [MMDDYYYY HH:MM:SS] -->
<!-- M-configuration: SAVING -->
## Tape Position (Current Focus)
[What you were actively working on — be specific]
## Symbol Table (Key Decisions)
| D.N. | Decision | Rationale | Confidence |
|------|----------|-----------|------------|
| D001 | [what] | [why] | [High/Medium/Low] |
## Modified Squares (Files Changed)
### Written (Created)
- `[path]` — [purpose]
### Overwritten (Modified)
- `[path]` — [what changed]
### Erased (Deleted)
- `[path]` — [why removed]
## Halt Conditions (Blockers)
- [Any blockers or pending items]
## Next Transitions (Action Queue)
1. [ ] [next action] — [expected outcome]
## Unresolved Symbols (Open Questions)
- [Questions requiring resolution]
## Context Tape (For Next Session)
[Free-form notes critical for continuity]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 178 lines · 21 tokens per session scan A b76699a4d27e
turing-save is a command published in the GitHub repository agenisea/turing (2 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 1,269 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
sample-command
A sample command for testing.
component
Command "component" from TidyFactor/Styler, covering command: component — create or redesign a single component, when to use, dispatch steps and do not load.
page
Command "page" from TidyFactor/Styler, covering command: page — build a new production page, when to use, dispatch steps and do not load.
section
Command "section" from TidyFactor/Styler, covering command: section — create or redesign a page section, when to use, dispatch steps and do not load.
redesign
Command "redesign" from TidyFactor/Styler, covering command: redesign — redesign an existing production page, when to use, dispatch steps and do not load.
rtl
The bar this command holds work to is already stated once, in SKILL.md's non-negotiable constraint 5 and in rtl-css-engineering.md itself — not repeated here.