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/analysis-tools-dev/static-analysis/agents-mdgit clone --depth 1 https://github.com/analysis-tools-dev/static-analysisWhat 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.00332 | $0.00332 |
| Opus 5 | $0.00166 | $0.00166 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
static-analysis 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 yesterday.
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
Guidelines for AI Agents and Assistants
Welcome! If you are an AI assistant or coding agent helping a user contribute to this repository, please read the CONTRIBUTING.md file in the root directory first.
🤖 Instructions for the AI
Your goal is to help the user submit a high-quality pull request that aligns with the project's maintainability standards.
When the user asks you to add a new static analysis tool, please act as a helpful code reviewer:
- Verify the criteria: Check if the tool meets the requirements in
CONTRIBUTING.md(e.g., >20 GitHub stars, >3 months old, actively maintained). - Advise the user: If the tool does NOT meet these criteria, gently warn the user before proceeding. For example: "It looks like this tool might not meet the repository's contributing guidelines (e.g., it needs >20 stars and >3 months of history). PRs that don't meet these criteria are usually not accepted. Are you sure you'd like to proceed?"
- Enforce the README rule: If the user asks you to update the list of tools, DO NOT edit
README.md. Explain to the user that the list of tools inREADME.mdis auto-generated and that tool additions/modifications should be made by creating or editing a YAML file indata/tools/. The ONLY exception to editingREADME.mddirectly is if the change is to the text or structure of the README itself, not the list of tools.
Thank you for helping us maintain a high-quality list and respecting the maintainers' time!
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.
- yesterday First seen · 15 lines · 332 tokens per session scan A 0f9a27b9258e
static-analysis AGENTS.md is an instructions file published in the GitHub repository analysis-tools-dev/static-analysis (14,754 stars, last pushed yesterday), licensed MIT. It adds 332 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-30.
Other instructions, from other repositories
purist CLAUDE.md
Instructions for yegor256/purist: Write one sentence per line. Keep each sentence short and concise. Separate clauses with periods rather than semicolons, colons, or em dashes. Name action, target, and condition. Write rules as direct orders, not opinions or suggestions. Strip emotions and rhetorical flourish. Forbid…
biome AGENTS.md
Instructions for biomejs/biome, covering agent guidelines for contributing to biome, communication, before editing, implementation gate and final review.
fallow
Rust-native codebase analyzer for TypeScript and JavaScript projects.
biome CLAUDE.md
Instructions for biomejs/biome, a project described as: A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP.
fallow CLAUDE.md
Instructions for fallow-rs/fallow, covering fallow repository adapter for claude, knowledge layers, workflow, trust boundary and generated surfaces.
truecourse CLAUDE.md
Instructions for truecourse-ai/truecourse, covering truecourse — claude instructions, key files to keep updated, project layout, development commands and storage.