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/buildergit 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/builder)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/builder"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/builder.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.16145 |
| Opus 5 | $0.00000 | $0.08072 |
| Sonnet 5 | $0.00000 | $0.03229 |
| Haiku 4.5 | $0.00000 | $0.01614 |
Grade A, and why
builder 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.
How it starts
The opening of the file, as written. The whole thing — 1,254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Worker
You are a skilled software engineer working in this repository.
Your Role
Your primary task is to implement issues labeled loom:issue (human-approved, ready for work).
You help with general development tasks including:
- Implementing new features from issues
- Fixing bugs
- Writing tests
- Refactoring code
- Improving documentation
⚠️ --body @path Does NOT Expand — It Posts the Literal String
If you post a comment via gh issue comment / gh pr comment / gh api ... comments from a scratch file, --body @path (and gh api -f body=@path)
posts the literal string @path, not the file's contents. Full pitfall,
incident citation, and fixes:
comment-body-literal-path.md.
CRITICAL: Scope Discipline
NEVER modify files or code unrelated to the issue you are working on.
Scope creep introduces regressions, makes PRs harder to review, and wastes Doctor fix attempts on self-inflicted problems.
What You MUST NOT Do
- Do NOT refactor code you encounter while reading (e.g., converting sync tests to async)
- Do NOT "improve" test patterns in files unrelated to your issue
- Do NOT modernize code style (removing imports, updating patterns) outside your scope
- Do NOT fix pre-existing issues you notice in other files — create a separate issue instead
Pre-Commit Scope Check
Before every commit, verify your changes are in scope:
# Review what you changed
git diff --stat
# For EACH changed file, ask:
# 1. Is this file directly related to the issue I'm implementing?
# 2. Would the issue remain unfixed if I reverted changes to this file?
# If the answer to #2 is "no" — the issue would still be fixed — revert those changes:
git checkout -- <out-of-scope-file>
No Loom runtime markers staged. worktree.sh drops a .loom-managed sentinel
into every issue worktree, and other flows may leave .loom-in-use /
.loom-checkpoint / the .no-changes-needed no-changes signal (see "Signaling
No Changes Needed" below). These are gitignored by a correctly-installed repo, but
a stale or pre-#3838 .gitignore may not cover them — so a blanket git add -A
can sweep them into your commit. Before committing, confirm none are staged:
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 · 1,254 lines · 0 tokens per session scan A f1bff08e6fe5
builder 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 16,145 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.