Borrowing it
Nothing to install: this file belongs to product-on-purpose/agent-skills-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/product-on-purpose/agent-skills-toolkit/main/AGENTS.mdgit clone --depth 1 https://github.com/product-on-purpose/agent-skills-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/product-on-purpose/agent-skills-toolkit/agents-md)<a href="https://agentmods.dev/instructions/product-on-purpose/agent-skills-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/product-on-purpose/agent-skills-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.1 | $0.01732 | $0.01732 |
| Opus 5 | $0.00866 | $0.00866 |
| Sonnet 5 | $0.00346 | $0.00346 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
agent-skills-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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - agent-skills-toolkit
Project-level instructions and navigation for any agent (Claude Code, Codex, or
other agentskills.io-compatible agents) working in this repository. This is the
agent-facing counterpart to the human-facing INDEX.md.
What this project is
agent-skills-toolkit is a self-hosting plugin and a versioned Standard for
authoring, validating, governing, and scaling cross-agent skill libraries. The
normative rules live in STANDARD.md (the Advanced Skill Library
Standard). The toolkit is built to its own Standard and, at v1, validates itself
against that Standard in CI.
The single source of truth for the rules is STANDARD.md. The consolidated
design and decision record is docs/internal/DESIGN.md.
Current state (read before assuming capabilities)
This repository declares tier: advanced (Gold) and self-validates against its
own Standard in CI - the deterministic validation spine lives in scripts/. The
full gate (Bronze U1-U9, U11-U18, Silver S1-S8, Gold G1-G10) is green and tier-report
reports tier: advanced with an empty burndown, so the toolkit is a self-proving
example of the Standard. See
docs/internal/BOOTSTRAP.md for historical context:
the one-time Bronze bootstrap that ended once the spine existed.
Components present on disk:
- Skills:
askit-evaluate(assess a skill or plugin against the Standard) plus theaskit-build-*builder family - one builder per component type (skill, subagent, command, mcp, hook, chain-contract, agents-md, output-style, and more as the catalog fills), each withcreate/improvemodes followingdocs/reference/builder-pattern.md. Core loop:askit-build-skill(create) ->askit-evaluate->askit-build-skill(improve). The exact current component list lives inlibrary.jsonandINDEX.md(this section stays terse on purpose - brevity is a feature). - Subagents:
askit-skill-author(the bounded authoring delegate behindaskit-build-skill) andaskit-evaluator(the read-only assessment delegate behindaskit-evaluate). Both are Claude-only (agent-targets: [claude]; Standard sec 3.3) and carry theaskit-prefix like every other component (sec 8.2). The chain contractagents/_chain-permitted.yamlpermits all five declared edges:askit-build-skill->askit-skill-author,askit-build-skill->askit-reviewer(the v1.7.0 craft pass, ADR 0037),askit-evaluate->askit-evaluator,askit-evaluate->askit-quality-grader,askit-evaluate->askit-reviewer, andaskit-skill-author->askit-evaluator. Read the file, not this list, when it matters:agents/_chain-permitted.yamlis the contract and this is a convenience summary. The full per-subagent reference isdocs/reference/subagents.md. - Commands:
/askit-evaluate(maps-to:askit-evaluate) and/askit-build-skill(maps-to:askit-build-skill). Commands are Claude-native; on Codex the backing skill is the invocable form (Standard sec 3.2). - Scripts: the Node validation spine in
scripts/- conformance checks, generators (gen-index,gen-manifest,sync-agents-md),tier-report.mjs, the aggregate gatecheck.mjs, andevaluate.mjs. - Silver checks (Convergent, reqId S1-S8) and Gold checks (Advanced, reqId G1-G10) gate the declared
tier: advancedalongside the Universal ones. S3 now validatescomponents.skills,components.subagents, andcomponents.commandsagainst disk. S4 orphan detection is complete: a frontmatterchain:invocation not permitted byagents/_chain-permitted.yamlis an orphan error; a contract entry naming a missing component is a phantom error. S6 checks per-target manifest presence at the plugin level. S7 (command-contract) checks that every command declares a non-emptydescriptionand amaps-toresolving to exactly one on-disk skill or workflow (conditional on commands existing). - Hooks, workflows: none yet (later phases).
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 Changed 1e3551d7b57f
- 8d ago First seen · 108 lines · 1,732 tokens per session scan A ac08238905a4
agent-skills-toolkit AGENTS.md is an instructions file published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,732 tokens to every session, about $0.0087 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.