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/stefan-jansen/coding-agent-toolkit/agents-mdgit clone --depth 1 https://github.com/stefan-jansen/coding-agent-toolkitWhat 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.01341 | $0.01341 |
| Opus 5 | $0.00671 | $0.00671 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
coding-agent-toolkit 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 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
coding-agent-toolkit
Contributor / maintainer notes. For the project introduction, see
README.md.
Purpose
Provide a small set of host-neutral workflow steps — align, plan,
plan-issues, next-issue, ship, handoff, continue — that take
a piece of work from rough idea to done, identically on Claude Code
and OpenAI Codex. The chain owns the structural work around producing
the thing: clarifying what "done" means, breaking it into chunks,
accumulating references and constraints as they surface, tracking
progress, carrying memory across sessions and host swaps, and
projecting state onto GitHub for review and version control. Local
state for each piece of work lives in .workspace/work/<unit>/ (spec,
plan, follow-up notes, references); GitHub is the public projection
(milestone / issues / branches / PRs / Closes #N). The dominant
deliverable is a merged PR; the chain drives non-code work too (a
research report, a course module, a long-form post) since the
projection doesn't care what the deliverable is. The actor is the
agent; this repository supplies the step definitions and the
file-shaped contract they share.
Cross-host primitive
The contract that makes the toolkit host-neutral is shared durable
state under .workspace/, read natively by both Claude Code and
Codex. There is no orchestrator. Either host runs a step; the step
writes files; the other host picks the state up by reading the same
files.
| Path | Role |
|---|---|
AGENTS.md (this file) |
Canonical project instructions. Codex reads natively; Claude includes via CLAUDE.md. |
CLAUDE.md |
One line — @AGENTS.md. |
.workspace/memory/ |
Persistent project memory; load on demand. |
.workspace/transitions/YYYY-MM-DD/HHMMSS.md |
/handoff output; /continue resumes from any of these on either host. |
.workspace/work/ |
Active work units (specs, plans, references, follow-up notes). |
Keep this contract tight. Never seed .claude/transitions/ or
.codex/state/ for new work; never invent a run-as-other-host
shortcut.
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 · 117 lines · 1,341 tokens per session scan A 67d9b1a5e98d
coding-agent-toolkit AGENTS.md is an instructions file published in the GitHub repository stefan-jansen/coding-agent-toolkit (22 stars, last pushed 16d ago), licensed MIT. It adds 1,341 tokens to every session, about $0.0067 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
n8n-skills CLAUDE.md
Instructions for czlonkowski/n8n-skills, covering claude.md, project overview, repository structure, the 14 skills and 1. n8n expression syntax.
Tutorial_AwesomeModernCPP AGENTS.md
Instructions for Awesome-Embedded-Learning-Studio/Tutorial_AwesomeModernCPP, covering agents.md, 这是什么, 通用 essentials(所有 agent 必读) and 你来做什么?(按场景路由).
python-cheatsheet copilot-instructions.md
Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.
fix-quera AGENTS.md
Instructions for AlirezaKeshavarz83/fix-quera, covering agent guidance, project shape, visual style, quera page data findings and compatibility findings.
ab900 CLAUDE.md
Instructions for timothywarner-org/ab900, covering claude.md, repository purpose, architecture, commands and 2. non-ascii punctuation -- must return zero.
agentconfig.org AGENTS.md
Instructions for agentconfig/agentconfig.org, covering agent instructions for agentconfig.org, project overview, target audience, site structure and tech stack.