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 instructions/shafthq/shaft_engine/gemini-mdgit clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINEWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/shafthq/shaft_engine/gemini-md)<a href="https://agentmods.dev/instructions/shafthq/shaft_engine/gemini-md"><img src="https://agentmods.dev/badge/instructions/shafthq/shaft_engine/gemini-md.svg" alt="Measured on agentmods" height="20"></a>What 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.00063 | $0.00063 |
| Opus 5 | $0.00032 | $0.00032 |
| Sonnet 5 | $0.00013 | $0.00013 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
SHAFT_ENGINE GEMINI.md 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 4d 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
Before every task, follow the canonical ChaosEngine. Use .chaos-engine/tool.py for the project-local Memory, MemPalace, and Graphify tools.
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.
- 4d ago First seen · 4 lines · 63 tokens per session scan A e7ade2a8d129
SHAFT_ENGINE GEMINI.md is an instructions file published in the GitHub repository ShaftHQ/SHAFT_ENGINE (407 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session, about $0.0003 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-30.
Other instructions, from other repositories
plugins CLAUDE.md
Claude Code instructions for ihub-pub/plugins, covering project knowledge base, project structure, plugin id 速查表, version compatibility and commands（build / lint / test）.
flyto-core AGENTS.md
AGENTS.md instructions for flytohub/flyto-core, covering flyto-core agent rules, flyto2 project memory contract, flyto2 frontend quality gate and repo notes.
alcove AGENTS.md
Instructions for epicsagas/alcove, covering claude.md, repository purpose, actual location, structure and karpathy 3-layer architecture.
state-memory-mcp copilot-instructions.md
Instructions for putervision/state-memory-mcp, covering state memory (state-memory-mcp), 1. priority order, 2. when to write to the graph, 3. workflow pattern and 4. codebase seeding on initialization.
toon-memory AGENTS.md
Instructions for LuiggiVal08/toon-memory, covering agents.md, build & verify, architecture, smarter memory pattern and visual memory pattern.
project-mem-mcp CLAUDE.md
Claude Code instructions for wallneradam/project-mem-mcp, covering claude.md, project overview, development commands, setup and run the server locally.