Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-pr)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/builder-pr"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/builder-pr.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.1 | $0.00000 | $0.11577 |
| Opus 5 | $0.00000 | $0.05789 |
| Sonnet 5 | $0.00000 | $0.02315 |
| Haiku 4.5 | $0.00000 | $0.01158 |
Grade A, and why
builder-pr 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 6d 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,109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builder: PR Creation and Quality
This document covers PR creation, test output handling, and quality requirements for the Builder role. For the core builder workflow, see builder.md.
Pre-Implementation Review: Check Recent Main Changes
CRITICAL: Before implementing, review recent changes to main to avoid conflicts with recent architectural decisions.
Why This Matters
The codebase evolves while you work. Recent PRs may have:
- Introduced new utilities or helper functions you should use
- Changed authentication/authorization patterns
- Updated API conventions or response formats
- Added shared components or abstractions
- Modified configuration or environment handling
Without this review: You may implement using outdated patterns, leading to merge conflicts, inconsistent code, or duplicated functionality.
Required Commands
Step 1: Review recent commits to main
# Show last 20 commits to main
git fetch origin main
git log --oneline -20 origin/main
# Show files changed in recent commits
git diff HEAD~20..origin/main --stat
Step 2: Check changes in your feature area
# Check recent changes in directories related to your feature
git log --oneline -10 origin/main -- "src/relevant/path"
git log --oneline -10 origin/main -- "*.ts" # or relevant file types
Step 3: Look for these architectural changes
| Change Type | What to Look For | Why It Matters |
|---|---|---|
| Authentication | New auth middleware, session handling, token patterns | Use the new auth approach, not old patterns |
| API Patterns | Response formats, error handling, validation | Match existing conventions |
| Utilities | New helper functions, shared modules | Reuse instead of reimplementing |
| Shared Components | Common UI elements, base classes | Extend rather than duplicate |
| Configuration | New env vars, config patterns | Follow established patterns |
Example Workflow
# 1. Fetch latest main
git fetch origin main
# 2. See what changed recently
git log --oneline -20 origin/main
# 5b55cb7 Add dependency unblocking to Guide role (#997)
# cc41f95 Add guidance for handling pre-existing lint/build failures (#982)
# 6b55a3e Add rebase step before PR creation (#980)
# ...
# 3. If you see relevant changes, investigate
git show 5b55cb7 --stat # See what files changed
git show 5b55cb7 # See the actual changes
# 4. Check changes in your feature area
git log --oneline -10 origin/main -- "src/lib/auth"
# -> If you see auth changes, read them before implementing!
# 5. Adapt your implementation plan based on findings
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.
- 6d ago First seen · 1,109 lines · 0 tokens per session scan A cef0538d50f2
builder-pr is a command published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 11,577 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.