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/jzfgo/agents/claude-mdgit clone --depth 1 https://github.com/jzfgo/agentsWrote 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/jzfgo/agents/claude-md)<a href="https://agentmods.dev/instructions/jzfgo/agents/claude-md"><img src="https://agentmods.dev/badge/instructions/jzfgo/agents/claude-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.00003 | $0.00003 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
agents 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 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.
This is a copy
100% identical to deepseek-harness CLAUDE.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
AGENTS.md
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 · 1 lines · 3 tokens per session scan A a54ff182c7e8
agents CLAUDE.md is an instructions file published in the GitHub repository jzfgo/agents (1 stars, last pushed 3mo ago), licensed MIT. It adds 3 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
gambit GEMINI.md
Instructions for felipecabargas/gambit, covering gambit, skills, core, discovery and communication.
gambit CLAUDE.md
Instructions for felipecabargas/gambit, covering gambit, available skills, core, discovery and communication.
SkillCheck-Free AGENTS.md
AGENTS.md instructions for olgasafonova/SkillCheck-Free, covering agent instructions, quick reference, landing the plane (session completion), issue tracking with bd (beads) and why bd?.
agentic-qa-boilerplate CLAUDE.md
Claude Code instructions for upex-galaxy/agentic-qa-boilerplate, a project described as: Agentic QA boilerplate built on Playwright + KATA + TypeScript. Multi-agent skills following the agentskills.io spec, orchestrating the full QA lifecycle: shift-left planning, in-sprint testing, TMS documentation with ROI scoring…
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
agent-skills AGENTS.md
AGENTS.md instructions for racastellanosm/agent-skills, covering agents.md, 1. vision & architectural invariants, 2. repository architecture & layout, 3. harness support & installation paths and 4. scripting & tooling guardrails.