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/dius/agent-toolkit/agents-mdgit clone --depth 1 https://github.com/DiUS/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.01150 | $0.01150 |
| Opus 5 | $0.00575 | $0.00575 |
| Sonnet 5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Working context and rules for any AI agent (or human) contributing to this repository:
the agent-toolkit repo itself, not the components it ships. CLAUDE.md imports this file and
adds Claude-Code-specific notes. Keep it lean: it loads into an agent's context every session.
What this repo is
agent-toolkit is DiUS's shared collection of skills, commands, agents and hooks for AI
coding agents. It ships two ways: as portable components installable with npx skills, and as
a single Claude Code plugin bundling skills, commands and agents.
For the catalogue of what's currently in the toolkit, see README.md. For how any
one component works, read that component's own entry point (a skill's SKILL.md, a command or
agent's frontmatter). This file is about contributing to the repo.
Repo map
skills/<name>/ Self-contained skills; everything a skill needs lives inside it.
commands/ Slash commands — single Markdown files with frontmatter.
agents/ Claude Code subagents a skill can delegate work to.
hooks/ Optional, opt-in Claude Code hooks — not wired into the plugin.
.claude-plugin/ Claude plugin + marketplace manifests.
docs/getting-started.md Per-tool install notes.
scripts/validate.js Verification gate (run before committing).
.github/workflows/validate.yml CI that runs the gate on push/PR.
Principles
- Host-agnostic first. Components should run on any capable agent. Do not add hard
dependencies on hooks, MCP servers, or a specific runtime. Optional integrations must degrade
gracefully: used when present, skipped cleanly when absent. Claude-specific wiring stays
confined to
.claude-plugin/,commands/,agents/andhooks/. - Skills are self-contained. Everything a skill's entry point references (playbooks,
references, templates) lives inside its own
skills/<name>/directory, which is the unitnpx skillsand the plugin install. Never point a skill file at something outside its own directory. - Lean docs. Docs (including this file) earn their length by making a contributor productive. Prefer prose and small tables; push depth into the specific file, not the index.
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 · 93 lines · 1,150 tokens per session scan A 958aae5ba7ff
agent-toolkit AGENTS.md is an instructions file published in the GitHub repository DiUS/agent-toolkit (2 stars, last pushed yesterday), licensed MIT. It adds 1,150 tokens to every session, about $0.0057 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
aider-desk AGENTS.md
Instructions for hotovo/aider-desk, covering agents.md, common commands, development, type checking and linting and formatting.
Meta_Kim CLAUDE.md
Instructions for KimYx0207/Meta_Kim, covering metakim for claude code, fast read, what this repository is, claude code's role and canonical vs runtime files.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.