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/ronald2wing/.gitignores/agents-mdgit clone --depth 1 https://github.com/ronald2wing/.gitignoresWrote 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/ronald2wing/.gitignores/agents-md)<a href="https://agentmods.dev/instructions/ronald2wing/.gitignores/agents-md"><img src="https://agentmods.dev/badge/instructions/ronald2wing/.gitignores/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.00641 | $0.00641 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
.gitignores 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Audience: AI agents operating on this repository.
Authoritative reference:TEMPLATE_STANDARDS.md
Architecture
Template factory — no build, lint, test, or package manager. Every template is a standalone .gitignore file.
Two Systems — pick one, never mix
| Framework | Modular | |
|---|---|---|
| Start | frameworks/<name>.gitignore |
languages/<name>.gitignore |
| Security | Built-in (first section) | Must add common/security.gitignore |
| Extras | IDEs, OS only | common/*, tools/*, ides/*, os/* |
Hard Constraints
- Framework + Language = NEVER — frameworks already contain language patterns.
- Language without Security = NEVER — add
common/security.gitignore. - Combine with
sort -u= ALWAYS —cat a b c | sort -u > .gitignore.
Creating or Editing
Language? → languages/<name>.gitignore (no security section)
Framework? → frameworks/<name>.gitignore (security section FIRST)
Tool/CI? → tools/<name>.gitignore
IDE? → ides/<name>.gitignore
OS? → os/<name>.gitignore
Platform? → platforms/<name>.gitignore
Naming, section ordering, header/metadata format → TEMPLATE_STANDARDS.md.
Section ordering gotcha: some existing templates (e.g. languages/rust.gitignore) have non-standard sections — new templates must follow the canonical order.
Combining Templates
- Pick core — Framework OR language, never both.
- Add security —
common/security.gitignorefor language templates. - Layer extras — Tools, IDEs, OS as needed.
- Deduplicate — pipe through
sort -u. - Validate —
git status --ignoredin a test repo.
Verification
# Dedup check (must produce no output)
sort template.gitignore | uniq -d
# Smoke test (adapt touch files to template patterns)
mkdir /tmp/gitignore-test && cd /tmp/gitignore-test && git init
cp /path/to/template.gitignore .gitignore
touch .env .env.local credentials.json secret.key
git status --ignored # All four should appear under "Ignored files"
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 · 78 lines · 641 tokens per session scan A 15297d3cd0ff
.gitignores AGENTS.md is an instructions file published in the GitHub repository ronald2wing/.gitignores (5 stars, last pushed 4mo ago), licensed MIT. It adds 641 tokens to every session, about $0.0032 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
github-mcp-server copilot-instructions.md
Copilot instructions for github/github-mcp-server, covering github mcp server - copilot instructions, project overview, critical build & validation steps, required commands (run before committing) and when modifying mcp tools/endpoints.
av CLAUDE.md
Claude Code instructions for aviator-co/av, covering claude.md, project overview, documentation sources, command structure philosophy and development workflow.
ghtkn AGENTS.md
AGENTS.md instructions for suzuki-shunsuke/ghtkn, a project described as: A CLI to create short-lived (8 hours) GitHub App User Access Token for secure local development.
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
dev_agent
Expert engineer for this GitHub Action.
msaccess-vcs-addin AGENTS.md
AGENTS.md instructions for joyfullservice/msaccess-vcs-addin, covering project overview, repository structure, architecture overview, component diagram and key architectural patterns.