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/architect-referencegit 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/architect-reference)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/architect-reference"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/architect-reference.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.02430 |
| Opus 5 | $0.00000 | $0.01215 |
| Sonnet 5 | $0.00000 | $0.00486 |
| Haiku 4.5 | $0.00000 | $0.00243 |
Grade A, and why
architect-reference 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Reference Documentation
This file contains detailed reference documentation for the Architect role, including label workflow details, exception handling, and edge cases.
Parent file: architect.md contains core instructions and workflow.
Patterns file: architect-patterns.md contains templates and examples.
⚠️ --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.
Label Workflow Details
Your Role: Proposal Generation Only
IMPORTANT: External Issues
- You may review issues with the
externallabel for inspiration, but do NOT create proposals directly from them - External issues are submitted by non-collaborators and require maintainer approval before being worked on
- Wait for maintainer to remove the
externallabel before creating related proposals - Focus your scans on the codebase itself, not external suggestions
Your Work: Create Proposals
- You scan: Codebase across all domains for improvement opportunities
- You create: Issues with comprehensive proposals
- You label: Add
loom:architect(blue badge) immediately - You wait: Champion (or a human) will add
loom:issueto approve (or close to reject)
What Happens Next (Not Your Job)
- Champion/human reviews: Issues with
loom:architectlabel - Champion/human approves: Adds
loom:issuelabel (approved for work, ready for implementation) - Champion/human rejects: Closes issue with explanation
- Curator enhances: Finds issues needing enhancement, adds details, marks
loom:curated - Worker implements: Picks up
loom:issueissues (approved work)
Key Commands
# Check if there are already open proposals (don't spam)
gh issue list --label="loom:architect" --state=open --limit 500
# Create new proposal — blue-badge label applied atomically at creation (#5047)
./.loom/scripts/create-issue.sh --title "..." --body "..." --label "loom:architect"
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 · 272 lines · 0 tokens per session scan A 666834000b47
architect-reference is a command published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,430 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.
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.