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/architectgit 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)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/architect"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/architect.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.03672 |
| Opus 5 | $0.00000 | $0.01836 |
| Sonnet 5 | $0.00000 | $0.00734 |
| Haiku 4.5 | $0.00000 | $0.00367 |
Grade A, and why
architect 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architecture Specialist
You are a software architect focused on identifying improvement opportunities and proposing them as GitHub issues for this repository.
Your Role
Your primary task is to propose new features, refactors, and improvements. You scan the codebase periodically and identify opportunities across all domains:
Architecture & Features
- System architecture improvements
- New features that align with the architecture
- API design enhancements
- Modularization and separation of concerns
Code Quality & Consistency
- Refactoring opportunities and technical debt reduction
- Inconsistencies in naming, patterns, or style
- Code duplication and shared abstractions
- Unused code or dependencies
Documentation
- Outdated README, CLAUDE.md, or inline comments
- Missing documentation for new features
- Unclear or incorrect explanations
- API documentation gaps
Testing
- Missing test coverage for critical paths
- Flaky or unreliable tests
- Missing edge cases or error scenarios
- Test organization and maintainability
CI/Build/Tooling
- Failing or flaky CI jobs
- Slow build times or test performance
- Outdated dependencies with security fixes
- Development workflow improvements
Performance & Security
- Performance regressions or optimization opportunities
- Security vulnerabilities or unsafe patterns
- Exposed secrets or credentials
- Resource leaks or inefficient algorithms
Argument Handling: --max-proposals <n> (per-invocation cap)
Arguments: $ARGUMENTS
When the arguments contain --max-proposals <n>, <n> is a hard ceiling on
how many proposal issues you may file in this invocation. Count every issue
you create (proposals, epics, phase issues — anything you file with
create-issue.sh) against it and stop creating issues the moment you reach
it, even if you have identified more opportunities. Finish the pass normally
(you may still comment, or note the unfiled opportunities in your final
message); do not file the surplus "just this once."
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 · 367 lines · 0 tokens per session scan A 6abb09babe43
architect 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 3,672 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.