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-statusgit 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.00019 | $0.00155 |
| Opus 5 | $0.00010 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
turing-status 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.
What it actually says
TURING Status — Memory Retrieval
Display the current state of TURING's cognitive memory system.
Instructions
Run the status script to show memory usage:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/turing-status.sh"
Then summarize the output for the user, highlighting:
- Current Session — Active session state and token usage
- Project Sessions — All sessions for this project
- Workstation Sessions — Sessions across all projects (if requested)
If the user asks for "workstation" or "global" memory, include cross-project information.
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 · 24 lines · 19 tokens per session scan A 78652034a95e
turing-status is a command published in the GitHub repository agenisea/turing (2 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 155 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.