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/tph-kds/deckforge/claude-mdgit clone --depth 1 https://github.com/tph-kds/deckforgeWhat 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.00092 | $0.00092 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
deckforge CLAUDE.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 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
DeckForge Claude Code Guide
Read AGENTS.md, then activate the relevant skill under skills/. The primary entry point is skills/deckforge/SKILL.md.
Keep the repository provider-portable. Do not add a production backend, database, authentication, billing, or deployment runtime here. Reference components are allowed under skills/deckforge/starter-components/ and must remain copyable, framework-clear, and free of secrets.
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 · 6 lines · 92 tokens per session scan A 82f1b2d476d4
deckforge CLAUDE.md is an instructions file published in the GitHub repository tph-kds/deckforge (4 stars, last pushed 16d ago), licensed MIT. It adds 92 tokens to every session, about $0.0005 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 instructions, from other repositories
deer-flow CLAUDE.md
Claude Code instructions for bytedance/deer-flow: The repo's agent guidance lives in AGENTS.md so it is shared across coding agents (Claude Code, Codex, and others). Claude Code imports it below.
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
sprawling AGENTS.md
Instructions for 2youg1/sprawling, covering agents.md — how work is done in this repository, the loop, read before you write, one change, five steps and the rules a machine holds.
sprawling CLAUDE.md
Instructions for 2youg1/sprawling: See AGENTS.md. It is the whole instruction set for this repository — the loop, what to read first, the five steps of one change, the rules a machine holds, and the language and commit conventions.
rn-dev-agent AGENTS.md
Instructions for Lykhoyda/rn-dev-agent, covering repository guide for agents, repository map, editing rules, architecture rules and supported node runtimes.
dirge CLAUDE.md
Claude Code instructions for dirge-code/dirge, covering project instructions for ai agents, beads issue tracker, quick reference, rules and session completion.