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/yeaight7/awesome-ai-devtools/agents-mdgit clone --depth 1 https://github.com/yeaight7/awesome-ai-devtoolsWrote 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/yeaight7/awesome-ai-devtools/agents-md)<a href="https://agentmods.dev/instructions/yeaight7/awesome-ai-devtools/agents-md"><img src="https://agentmods.dev/badge/instructions/yeaight7/awesome-ai-devtools/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.00344 | $0.00344 |
| Opus 5 | $0.00172 | $0.00172 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
awesome-ai-devtools 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 4d 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 Guidance
This repository is metadata-first. Do not hand-edit generated tool listings in README.md or docs/COMPARISON.md — both are generated.
Source Of Truth
- Edit
data/tools.yml,data/categories.yml, anddata/tags.yml. - Run
npm run sortafter changing tool metadata. - Run
npm run generateafter changing data or README generation. - Run
npm testbefore claiming completion. - Network-dependent maintenance (
npm run check:links,npm run check:stale) runs in the scheduled workflow, never in PR validation. Seedocs/maintenance-policy.md.
Data Rules
- Use official sources wherever possible.
- Do not invent metadata. Use
not specifiedfor uncertain license, deployment, or source-model facts. - Keep descriptions factual, neutral, and 40-180 characters.
- Do not add subjective rankings, scores, hype language, or launch strategy. Validation rejects promotional description language and warns on soft subjective wording.
- Do not add large batches manually. Use
scripts/import-candidates.tsfor candidate batches, then review entries before promotion. - Imported entries remain drafts until sources, categories, and uncertain fields are verified.
- When promoting a multi-category tool to
reviewed, setprimary_categoryto the single category slug that best represents its primary workflow. Validation will block promotion without it.
Scope Boundaries
- Do not add dependencies, CI changes, scraping, auth, deployment, or website work unless explicitly requested.
- Keep diffs small and reversible.
- Public contribution policy belongs in
CONTRIBUTING.mdanddocs/, not only here.
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.
- 4d ago First seen · 28 lines · 344 tokens per session scan A f578477687cd
awesome-ai-devtools AGENTS.md is an instructions file published in the GitHub repository yeaight7/awesome-ai-devtools (10 stars, last pushed 6d ago), licensed MIT. It adds 344 tokens to every session, about $0.0017 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
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
awesome-python AGENTS.md
AGENTS.md instructions for vinta/awesome-python, covering agents.md and entry rules.
awesome-quant AGENTS.md
AGENTS.md instructions for wilsonfreitas/awesome-quant, covering agents.md, project overview, architecture, work tracking and planning and commands.
awesome-ai-gateway CLAUDE.md
Claude Code instructions for cuihuan/awesome-ai-gateway, covering claude.md — working rules for this repository, what this repository is, the two goals — judge every change against these, non-negotiable rules and before you commit.
awesome-ai-scientists CLAUDE.md
Instructions for natnew/awesome-ai-scientists, covering claude.md, north star, resolver — load per task, first-pass workflow and stop conditions.
awesome-rss-feeds-list AGENTS.md
Instructions for xiangyugongzuoliu/awesome-rss-feeds-list, covering agents.md, build & test, code style and boundaries.