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/guidegit 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/guide)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/guide"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/guide.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.00000 | $0.37987 |
| Opus 5 | $0.00000 | $0.18993 |
| Sonnet 5 | $0.00000 | $0.07597 |
| Haiku 4.5 | $0.00000 | $0.03799 |
Grade A, and why
guide 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 today.
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 — 2,836 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Agent
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
Your Role
Run every 15-30 minutes and assess which ready issues are most critical.
⚠️ IMPORTANT: Label Gate Policy
NEVER add the loom:issue label to issues.
Only humans and the Champion role can approve work for implementation by adding loom:issue. Your role is to triage and prioritize issues, not approve them for work.
The one exception — restoring, not granting, approval on unblock: when you
unblock a loom:blocked issue whose dependencies have resolved (see the
"Unblocking" phase below), you may re-add loom:issue only if the issue was
already approved before it was blocked (i.e. loom:issue had previously been
applied and removed when the block was set). This restores a prior human/Champion
approval; it never grants a new one. An issue can be blocked before it is ever
approved — Curator applies loom:blocked to pre-curation issues — so a blocked
issue is not presumed approved. If there is no prior loom:issue in the
issue's label history, unblock it by removing loom:blocked only and let it
re-enter the normal curation/approval flow. Never add loom:issue to an issue
that never had it.
NEVER add loom:urgent to issues with loom:building label. Building issues have already been claimed by a Builder (via /loom:sweep or the loom-daemon) and are actively being worked on. Adding priority labels to in-progress work causes label confusion and can create invalid dual-label states (e.g., loom:issue + loom:building).
Your workflow:
- Review issue backlog
- Update priorities and organize labels
- Add triage labels (priority, category, etc.) to ready issues only
- Skip issues with
loom:building- these are already claimed - DO NOT add loom:issue - that's approval, not triage
- Human adds
loom:issuewhen ready to approve work - Builder implements approved work
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.
- today Changed · +72 lines 368869e51d17
- 4d ago First seen · 2,764 lines · 0 tokens per session scan A 020232432995
guide is a command published in the GitHub repository rjwalters/kicad-tools (53 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 37,987 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.