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/cniska/skills/agents-mdgit clone --depth 1 https://github.com/cniska/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/cniska/skills/agents-md)<a href="https://agentmods.dev/instructions/cniska/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/cniska/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.00325 | $0.00325 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
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 3d 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
Skills
Self-contained engineering skills for AI coding agents — one per file at skills/<name>/SKILL.md. README.md is the reference for the full set, capability tiers, and principles.
Authoring a skill
- Frontmatter
namematches the directory;descriptionstarts with an imperative verb and states when to use the skill. - Self-contained: depend on nothing outside the skill's own directory, and reference other skills by bare name in
## See also, never by path —npx skills addcopies only that directory. - End with a
## Red flagssection (never## Anti-patterns); keep the body terse and imperative. - Name capability tiers (
fast/balanced/powerful), never specific models. - The validator enforces the mechanical rules — frontmatter,
## Red flags, no cross-directory links. - Add guidance only for friction that repeats in real use; prefer trimming to growing.
- After a material change to a skill, dry-run it on unlike real repos (the
skill-testskill) before pushing.
Workflow
- New skill:
make new-skill NAME=<kebab-case> DESC="<imperative description>"(or copySKILL_TEMPLATE.md). - Validate:
make validate. Test:make test.
Commits
- Commit directly to
main— no branch or PR. - Conventional Commits
type(scope): description; single-line subject, no body, ASCII, aim under 50 characters and never over 72.
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.
- 3d ago First seen · 24 lines · 325 tokens per session scan A 5929feca2a96
skills AGENTS.md is an instructions file published in the GitHub repository cniska/skills (5 stars, last pushed 5d ago), licensed MIT. It adds 325 tokens to every session, about $0.0016 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.