Borrowing it
Nothing to install: this file belongs to buYoung/skills. 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/buYoung/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/buYoung/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/buyoung/skills/agents-md)<a href="https://agentmods.dev/instructions/buyoung/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/buyoung/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.1 | $0.01908 | $0.01908 |
| Opus 5 | $0.00954 | $0.00954 |
| Sonnet 5 | $0.00382 | $0.00382 |
| Haiku 4.5 | $0.00191 | $0.00191 |
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 6d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
1. Overview
This repository maintains portable AI agent skill packages and the release/catalog metadata that makes those packages installable across agent runtimes. Each skill owns its own activation contract, domain references, examples, validators, and revision evidence.
2. Ownership Map
Stable Ownership Boundaries
- Skill package contract: Start in
skills/<skill-name>/SKILL.mdwhen changing a skill's trigger, workflow, output contract, or guardrails. It owns the public activation surface consumed by README catalog entries and marketplace bundles, and must preserve package-local routing intoreferences/,scripts/,examples/,evals/, orupdates/; verify by checking the skill entry point plus any linked package-local artifacts. - Reference and artifact boundary: Start in the owning package's
references/,examples/,evals/, orupdates/when changing detailed domain rules, sample outputs, regression material, or design notes. These files extend the owningSKILL.mdwithout becoming shared repository policy; verify that relative links from the entry point still resolve and that examples/evals still match the documented output shape. - Structural validator boundary: Start in the owning package's
scripts/directory when changing machine-checkable document shape. Validators use standard-library Python with constants, regex contracts, explicit exit codes, andReportobjects, and they must remain structural checks rather than semantic judges; verify through the script's own usage contract and representative fixture or target document. - Release and marketplace boundary: Start in
scripts/release/,.release-it.json,.claude-plugin/marketplace.json, README availability tables, and both changelogs when changing published bundle membership, package versioning, or release notes. These files form one metadata chain, so bundle paths, advertised availability, generated changelog sections, and tag workflow checks must stay aligned. - Repository guidance boundary: Start in root
AGENTS.md,fable5.md, anddocs/when changing agent-facing repository policy or operating guidance. Repository-level guidance applies across skill packages, while package-specific rules stay beside the owning skill; verify that generated or managed sections preserve custom user sections and do not duplicate package-owned details.
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.
- 6d ago First seen · 60 lines · 1,908 tokens per session scan A 1fb01ea84c95
skills AGENTS.md is an instructions file published in the GitHub repository buYoung/skills (20 stars, last pushed 8d ago), licensed MIT. It adds 1,908 tokens to every session, about $0.0095 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-30.
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.