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/alphabetc1/agent-skills/agents-mdgit clone --depth 1 https://github.com/alphabetc1/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/alphabetc1/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/alphabetc1/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/alphabetc1/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.1 | $0.00370 | $0.00370 |
| Opus 5 | $0.00185 | $0.00185 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
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 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.
What it actually says
Agent Skills Repo Rules
This repository is an agent-skills repository.
When you add or update a skill in this repository, you must follow these rules:
Required layout
- Create the skill under
skills/<name>/. - Add at least:
README.mdSKILL.mdinstall.sh
- If the skill should support native PowerShell installation, also add
install.ps1. - Keep scripts, assets, examples, references, docs, and any other skill-specific files inside that skill's own directory.
- Do not place skill-specific files at the repository root.
Discovery rules
- The root installers auto-discover installable skills from
skills/*/install.shandskills/*/install.ps1. - Do not add manual registration code to the root installers just to make a new skill discoverable.
- Ensure
skills/<name>/install.shis executable, otherwise the root Bash installer will not list or install the skill.
Documentation rules
- Update the root
README.mdwhen a new skill is added. - Add the new skill to the root skills table.
- Add a detailed section for the new skill if it is intended to be user-facing.
- Every new skill must include a complete architecture diagram and flow diagram in its own
README.md.
Behavior rules for agents
- If a requested skill does not fit this repository layout, stop and explain the conflict instead of inventing a new structure.
- Prefer small, repo-consistent changes over creating parallel conventions.
- Before finishing, run:
python scripts/validate_skill_layout.py
Or validate a single skill:
python scripts/validate_skill_layout.py <name>
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 · 46 lines · 370 tokens per session scan A 2f79d1dba512
agent-skills AGENTS.md is an instructions file published in the GitHub repository alphabetc1/agent-skills (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 370 tokens to every session, about $0.0019 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).
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).
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.
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.
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.