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/rapiercraftstudios/forgedock/agents-mdgit clone --depth 1 https://github.com/RapierCraftStudios/ForgeDockWhat 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.00570 | $0.00570 |
| Opus 5 | $0.00285 | $0.00285 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
ForgeDock 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 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 55 lines · 570 tokens per session scan A 3e575b3a24d0
ForgeDock AGENTS.md is an instructions file published in the GitHub repository RapierCraftStudios/ForgeDock (118 stars, last pushed 24d ago), licensed AGPL-3.0. It adds 570 tokens to every session, about $0.0029 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
evolve-loop AGENTS.md
Instructions for mickeyyaya/evolve-loop, covering agents.md — cross-cli canonical instructions, what evolve-loop is, cross-cli invariants (the universal rules), 1. pipeline ordering is non-negotiable and 4. builder writes only inside its worktree.
evolve-loop CLAUDE.md
Instructions for mickeyyaya/evolve-loop, covering project instructions (claude code), automation loop guardrails, status reporting, session conventions and autonomous execution (bypass mode).
evolve-loop GEMINI.md
Instructions for mickeyyaya/evolve-loop, covering project instructions (gemini cli), skill discovery, runtime adapter (tier-1-hybrid), tool name translation and invariants (apply to gemini context too).
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
nimbalyst AGENTS.md
AGENTS.md instructions for nimbalyst/nimbalyst: At the beginning of every AI session, read the root CLAUDE.md and any applicable package-level CLAUDE.md before taking actions.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).