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/shyuan/skills/agents-mdgit clone --depth 1 https://github.com/shyuan/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/shyuan/skills/agents-md)<a href="https://agentmods.dev/instructions/shyuan/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/shyuan/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.00655 | $0.00655 |
| Opus 5 | $0.00328 | $0.00328 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
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 5d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents working in this repository. Human contributors: see CONTRIBUTING.md.
What this repo is
A curated catalog of Agent Skills. It is not an application — there is no build, no test suite, no package to publish. Each skill is a self-contained folder that another agent consumes; the repo's job is to keep those folders correct and discoverable.
Layout
skills/
<skill-name>/
SKILL.md # required: frontmatter (name, description) + instructions
references/ # optional: deep-dive docs loaded on demand
scripts/ # optional: executable helpers
assets/ # optional: checklists, templates
Flat structure — one level of skill folders under skills/, no category buckets.
Invariants (keep these true)
- Every skill folder contains a
SKILL.mdwith YAML frontmatter that has at leastnameanddescription. - The folder name equals the
namein frontmatter, in lowercase-kebab-case. - Every skill is listed in the Skills table in README.md, with its name linked to its folder. Adding or removing a skill means updating that table in the same change.
- Scripts are committed with the executable bit set (
git ls-files -sshows100755), so they run after a clone. - Machine-local agent config (e.g.
.claude/settings.local.json) is never committed; it is gitignored. Don't add it back.
Editing skills
- Treat each
SKILL.md'sdescriptionas load-bearing: it is what an agent reads to decide whether to invoke the skill. When you change behavior, keep the description's triggers and not-for notes accurate. - Keep
SKILL.mdfocused; put long material inreferences/so it loads only when needed. - Don't rename a skill folder without updating the frontmatter
nameand the README table together.
Third-party content
Some skills bundle material from other projects. Preserve the upstream license and attribution exactly:
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.
- 5d ago First seen · 62 lines · 655 tokens per session scan A b0c5900c4314
skills AGENTS.md is an instructions file published in the GitHub repository shyuan/skills (5 stars, last pushed 10d ago), licensed MIT. It adds 655 tokens to every session, about $0.0033 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).
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.
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).