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/denysdovhan/agents/agents-mdgit clone --depth 1 https://github.com/denysdovhan/agentsWrote 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/denysdovhan/agents/agents-md)<a href="https://agentmods.dev/instructions/denysdovhan/agents/agents-md"><img src="https://agentmods.dev/badge/instructions/denysdovhan/agents/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.00525 | $0.00525 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
agents 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.
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.
Repository Guidelines
Project Structure & Module Organization
This repository contains reusable agent skills:
skills/<skill-name>/SKILL.mdis required for every skill.skills/<skill-name>/agents/openai.yamlcontains optional OpenAI UI metadata.skills/<skill-name>/assets/contains icons and other bundled assets.skills/<skill-name>/references/contains longer supporting docs.scripts/contains repository tooling..github/workflows/contains CI configuration..skill-ref/is a local bootstrap clone for validation tooling; do not edit it as source.
Build, Test, and Development Commands
Run all validation before finishing skill changes:
./scripts/validate-skills.sh
This bootstraps skills-ref into .skill-ref/skills-ref if needed and
validates every skill under skills/. To validate one skill directly after the
bootstrap exists, run:
.skill-ref/skills-ref/.venv/bin/skills-ref validate skills/commit
There is no build step; this is a documentation and asset repository.
Coding Style & Naming Conventions
Use Markdown for skill instructions and YAML for metadata. Skill directory names
must match the name field in SKILL.md, using lowercase hyphenated names
such as home-assistant-integration. Keep SKILL.md focused on actionable
workflow guidance. Put reusable reference material in references/ instead of
expanding the main skill file unnecessarily. Use relative asset paths in
agents/openai.yaml, for example ./assets/git.png.
When creating or substantially updating skills, all agents must use the
skill-creator skill and follow its guidance before editing skill files.
Testing Guidelines
Validation is schema-based through skills-ref; there are no unit tests or
coverage targets. Add or update assets and references only when they are used by
a skill or its metadata. After changing SKILL.md, metadata, references, or
assets, run ./scripts/validate-skills.sh and git diff --check.
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 · 62 lines · 525 tokens per session scan A c486069ddc24
agents AGENTS.md is an instructions file published in the GitHub repository denysdovhan/agents (17 stars, last pushed 1mo ago), licensed MIT. It adds 525 tokens to every session, about $0.0026 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
claude-code-tresor CLAUDE.md
Instructions for alirezarezvani/claude-code-tresor, covering claude.md - development guide, 🎯 repository purpose, 🏗️ architecture, 🛠️ common development commands and building & testing.
skills AGENTS.md
Instructions for vanducng/skills, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and documentation sync.
Product-Marketing-Skills CLAUDE.md
Instructions for stefanoskarakasis/Product-Marketing-Skills, covering claude.md, versioning & releases, release procedure (manual, until ci enforcement exists) and after any repo change.
avvarre CLAUDE.md
Instructions for PralhadYadawad/avvarre, covering avvarre — claude code instructions, what is avvarre?, available slash commands, mcp tools and project memory (.avvarre/).
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
lumen AGENTS.md
AGENTS.md instructions for ory/lumen, covering agents.md, repository expectations and commands.