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/ahgraber/skills/agents-mdgit clone --depth 1 https://github.com/ahgraber/skillsWrote 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/ahgraber/skills/agents-md)<a href="https://agentmods.dev/instructions/ahgraber/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/ahgraber/skills/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.02158 | $0.02158 |
| Opus 5 | $0.01079 | $0.01079 |
| Sonnet 5 | $0.00432 | $0.00432 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade C, and why
skills AGENTS.md scanned grade C with 1 finding 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 today.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Use `git agent-commit` (not `git commit`) to create signed commits; this alias uses the dedicated agent signing key at `~/.ssh/id_ed25519_agent_signing`. How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repo holds Agent Skills, folders of instructions, scripts, and resources - typically encoding procedural knowledge - that agents can discover and use to do things more accurately and efficiently.
See skills/optimize-skills for best practices on designing skills.
Avoid adding extra documentation files inside skills unless explicitly required. Do not manually add linebreaks, trust linters and formatters for this.
Source skills vs. installed skills
- This repo is the upstream source for the skills it contains. The agent assisting on this repo may have overlapping skills installed (visible in its available-skills list); those installed copies are downstream consumers and may be stale or diverged.
- All work in this repo — edits, reviews, refactors, tests — must target the repo variant under skills/. Never operate against the installed version surfaced to the agent.
- Corollary (pressure-testing): if the user asks to pressure-test, exercise, or critique a skill defined in this repo, work against the repo variant by reading skills/<name>/SKILL.md (and its references) directly.
Do not invoke the installed copy via the
Skilltool — that loads a potentially divergent version and gives misleading results.
Development vs. user environment
- These practices describe how we develop and test skills in this repo.
- IMPORTANT: Do not assume end users who install skills have the same tools available; only
uvis a required runtime dependency (per the README). - When documenting or scripting behavior, distinguish between developer-only tooling (devshell,
dot,nix) and what a user can be expected to have.
Dev environment
- Prefer working inside the Nix devshell for tool availability (e.g.,
dot). - Enter the shell with:
nix develop
flake.nixis the source of truth for devshell packages.
Python scripts (skills//scripts/.py)
- Use
uvinline script metadata for dependencies (nopyproject.toml). - Required header format:
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.
- today Changed · +1 tokens per session c7ee1b408a29
- 4d ago First seen · 138 lines · 2,157 tokens per session scan C 1ed040f1de7c
skills AGENTS.md is an instructions file published in the GitHub repository ahgraber/skills (5 stars, last pushed yesterday), licensed CC0-1.0. It adds 2,158 tokens to every session, about $0.0108 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). 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.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-release stance: foundation over blast radius, repository layout, commands and host sandbox failures.