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/copilot-instructionsgit clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINEWhat 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.00146 | $0.00146 |
| Opus 5 | $0.00073 | $0.00073 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
SHAFT_ENGINE copilot-instructions.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 3d 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
SHAFT_ENGINE Copilot Instructions
Follow AGENTS.md as the canonical repository policy.
- Load
.agents/skills/chaos-engine/SKILL.md; scoped instruction and skill files are adapters to its internal playbooks. - Prefer targeted reads and deterministic local checks; reuse valid evidence.
- Preserve unrelated work and never expose secrets or claim unverified remote results.
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.
- 3d ago First seen · 13 lines · 146 tokens per session scan A 074c84ef07a4
SHAFT_ENGINE copilot-instructions.md is an instructions file published in the GitHub repository ShaftHQ/SHAFT_ENGINE (407 stars, last pushed yesterday), licensed MIT. It adds 146 tokens to every session, about $0.0007 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
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
rosetta AGENTS.md
Instructions for tikoci/rosetta, covering codex instructions for rosetta, first reads, development defaults and mcp and client config.
pharo-smalltalk-interop-mcp-server CLAUDE.md
Instructions for mumez/pharo-smalltalk-interop-mcp-server, covering claude.md, project overview, development setup, environment variables and common commands.
rosetta llm-instruction-files-excluded-from-mdlint.instructions.md
LLM-targeted instruction files are excluded from markdownlint so authoring rules for human docs do not distort agent-facing guidance.
mcp-server-powerpoint code-review.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering copilot code review, interop and resource safety, contract and path completeness and protocol, tests, and user-facing surfaces.