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/anthonyposchen/agent-skills/agents-mdgit clone --depth 1 https://github.com/AnthonyPoschen/agent-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/anthonyposchen/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/anthonyposchen/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/anthonyposchen/agent-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.00415 | $0.00415 |
| Opus 5 | $0.00208 | $0.00208 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
agent-skills 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.
What it actually says
Agent Skills Repository Guide
This repository publishes reusable Agent Skills. Keep the repo easy for installers and agents to scan.
Structure
- Put every public skill in
skills/<skill-name>/. - Use lowercase kebab-case for skill folders.
- Every skill must contain
SKILL.md. - Optional supporting resources belong in
scripts/,references/,assets/, oragents/. - Do not add README files inside individual skill directories; put public docs
in the repo README and agent instructions in
SKILL.md.
Skill Rules
SKILL.mdfrontmatter must contain onlynameanddescriptionunless a specific consuming tool requires more.- The
namevalue should match the folder name. - Put all activation and routing language in
description. - Prefer concise, imperative instructions in the body.
- Link directly from
SKILL.mdto supporting reference files so agents can load them only when relevant. - Add scripts only when they make repeated or fragile work more reliable.
- When adding a new skill folder, run
npm run link-skillsso the local~/.agents/skills/<skill-name>entry exists before validation.
Validation
Run this before publishing changes:
npm run validate
The validator checks skill folder names, frontmatter boundaries, required
fields, duplicate names, references to missing local markdown files, and local
entries in ~/.agents/skills for every skills/<skill-name>/ directory.
Releases
- Always prepare release notes when cutting a release unless the user explicitly says to skip release notes.
- If changelog or release-note evidence exists (
CHANGELOG.md,docs/releases/,docs/changelog/,releases/, or.github/releases/), update it before tagging. - In-repo changelog or release-note updates must be committed before tagging.
- Tag the commit that includes required release-note updates.
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 · 50 lines · 415 tokens per session scan A 4c1abc74d379
agent-skills AGENTS.md is an instructions file published in the GitHub repository AnthonyPoschen/agent-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 415 tokens to every session, about $0.0021 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.