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/moberghr/mtk-agent-toolkit/agents-mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/agents-md)<a href="https://agentmods.dev/instructions/moberghr/mtk-agent-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/moberghr/mtk-agent-toolkit/agents-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.02414 | $0.02414 |
| Opus 5 | $0.01207 | $0.01207 |
| Sonnet 5 | $0.00483 | $0.00483 |
| Haiku 4.5 | $0.00241 | $0.00241 |
Grade A, and why
mtk-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 4d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MTK Agent Routing
Compatible with: Claude Code, Codex CLI, Cursor, Copilot, Windsurf, and other AI coding tools that read AGENTS.md.
This repository uses skills as both user-facing entry points and reusable workflow blocks, and agents as specialist reviewers. There are two user-invocable slash commands — /mtk-setup (first-time setup + re-audit) and /mtk <description> (router for everything else). Workflow skills are composed by these entry points.
Routing Decision Tree
flowchart TD
START["New task"] --> Q1{"What kind<br/>of task?"}
Q1 -- "New feature /<br/>breaking change /<br/>> 3 files" --> FEAT["Load skills:"]
Q1 -- "Bug / regression /<br/>failing test" --> BUG["Load skills:"]
Q1 -- "Code review /<br/>PR review /<br/>quality audit" --> REV["Load skills:"]
Q1 -- "Creating or<br/>modifying a skill" --> SKILL["Load skills:"]
Q1 -- "Engineer corrects<br/>your approach" --> CORR["correction-capture"]
Q1 -- "You struggled 2+ times,<br/>then found what works" --> GOLD["golden-path-capture"]
FEAT --> F1["context-engineering"]
F1 --> F1b["brainstorming<br/><i>if approach unclear</i>"]
F1b --> F2["spec-driven-development"]
F2 --> F3["planning-and-task-breakdown"]
F3 --> F4["incremental-implementation"]
F4 --> F5["test-driven-development"]
F5 --> F6["source-driven-development<br/><i>if framework uncertain</i>"]
F6 --> F7["verification-before-completion"]
F7 --> F8["using-git-worktrees<br/><i>if isolation needed</i>"]
BUG --> B1["context-engineering"]
B1 --> B2["debugging-and-error-recovery"]
B2 --> B3["test-driven-development<br/><i>if behavior changes</i>"]
B3 --> B4["verification-before-completion"]
REV --> R1["context-engineering"]
R1 --> R2["code-review-and-quality"]
R2 --> R3["security-and-hardening<br/><i>if auth/secrets/audited state</i>"]
SKILL --> S1["writing-skills"]
S1 --> S2["Create pressure tests<br/>in tests/pressure-tests/"]
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.
- 4d ago First seen · 168 lines · 2,414 tokens per session scan A ea2d5443f4bd
mtk-agent-toolkit AGENTS.md is an instructions file published in the GitHub repository moberghr/mtk-agent-toolkit (7 stars, last pushed 9d ago), licensed MIT. It adds 2,414 tokens to every session, about $0.0121 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.