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/woodwosj/ghostshell/agents-mdgit clone --depth 1 https://github.com/woodwosj/GhostShellWhat 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.00143 | $0.00143 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
GhostShell AGENTS.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 yesterday.
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.
This is a copy
100% identical to 1code AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
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.
- yesterday First seen · 18 lines · 143 tokens per session scan A 989371119443
GhostShell AGENTS.md is an instructions file published in the GitHub repository woodwosj/GhostShell (0 stars, last pushed 1mo ago), licensed MIT. It adds 143 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to 1code AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
latchkey AGENTS.md
Instructions for imbue-ai/latchkey: For information about the high-level goal and motivations, see README.md.
hush AGENTS.md
Instructions for royashbrook/hush, covering agents.md, for any agent, not just one tool, what hush is (one line), install (any agent) and then read skill.md.
treg CLAUDE.md
Claude Code instructions for superdesigndev/treg, covering tools-registry (treg), words to use, and words not to, do not document what is not built, repo conventions and development.
treg AGENTS.md
AGENTS.md instructions for superdesigndev/treg, covering agents.md — guide for ai coding agents, read first, working agreement, do not touch (without reading the fragment first) and security awareness.
kdbx AGENTS.md
Instructions for yarrasys/kdbx, covering agents.md, what this is, current status — read this first, golden rules and repository map.
xaip-protocol AGENTS.md
AGENTS.md instructions for xkumakichi/xaip-protocol, covering agents.md — ai-assisted contribution guide, 1. public wording boundaries, 2. commit and pr rules, 3. privacy rules and 4. verification before commit.