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 commands/rjwalters/kicad-tools/gitignoregit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/commands/rjwalters/kicad-tools/gitignore)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/gitignore"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/gitignore.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.00019 | $0.01447 |
| Opus 5 | $0.00010 | $0.00724 |
| Sonnet 5 | $0.00004 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
gitignore 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo:gitignore — Gitignore Audit
Check that gitignore rules are appropriate for this repository. Catches files that shouldn't be ignored and build artifacts that should be.
Usage
/repo:gitignore # Full repo — apply clear rule fixes, report as you go
/repo:gitignore data/ # Check one subtree
/repo:gitignore --ask # Review findings and confirm before editing
Context First
Determine whether the repo is public or private before judging rules
(gh repo view --json isPrivate --jq .isPrivate, or ask the user if there is
no GitHub remote). The right answer differs:
- Private repos often want data files, docs, and notes tracked — flag rules that hide them.
- Public repos often want those same files ignored — flag tracked files that look like they leaked in (credentials, dumps, personal notes are critical findings either way).
What It Checks
1. Over-Ignored Files
Flag gitignore rules that exclude things that look like real content:
- Data files (.yaml, .json, .csv) that aren't build output
- Documentation or notes
- Configuration that isn't secrets
Always keep ignored, in any repo:
.envfiles and anything credential-likenode_modules/,.venv/,__pycache__/- Build output (
dist/,build/,target/,*.pyc) - IDE files (
.vscode/,.idea/) - OS files (
.DS_Store)
2. Under-Ignored Files
Find tracked files that are probably build artifacts:
*.pyc,__pycache__/dist/,build/, coverage output- Large binaries that look generated (
.o,.so,.whl)
3. Gitignore Hygiene
- Redundant rules (already covered by a parent
.gitignore) - Rules that match zero files (stale after cleanup)
- Scattered
.gitignorefiles that could be consolidated
Do not flag X and X/ as duplicates without verification. A trailing
slash restricts a gitignore pattern to directories — it never matches a
symlink, even one that points at a directory (man gitignore: "If there is a
separator at the end of the pattern then the pattern will only match
directories"). The two rules are therefore not interchangeable:
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 · 136 lines · 19 tokens per session scan A 5fb67f6dbbc7
gitignore is a command published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,447 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.