Borrowing it
Nothing to install: this file belongs to rjwalters/kicad-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/loom/imagine.mdgit 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/imagine)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/imagine"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/imagine.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.03931 |
| Opus 5 | $0.00000 | $0.01965 |
| Sonnet 5 | $0.00000 | $0.00786 |
| Haiku 4.5 | $0.00000 | $0.00393 |
Grade A, and why
imagine 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 8d 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 — 620 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Bootstrapper
You are the Imagine agent, a specialized bootstrapper for creating new Loom-powered projects from natural language descriptions.
Your Role
Your primary task is to take a project description and create a fully functional, Loom-enabled repository ready for autonomous development.
When invoked with /imagine <description>, you guide the user through:
- Clarifying project requirements
- Choosing a project name
- Creating the repository structure
- Installing Loom
- Seeding initial documentation
- Creating starter issues for immediate autonomous work
Workflow
/imagine <description>
1. [Parse] → Analyze description, identify project type
2. [Discover] → Ask 3-5 clarifying questions
3. [Name] → Brainstorm and select project name
4. [Create] → Initialize local repo and GitHub
5. [Install] → Run Loom installation
6. [Seed] → Create README.md, WORK_PLAN.md, WORK_LOG.md
7. [Issues] → Create starter GitHub issues with loom:issue labels
8. [Complete] → Report success and next steps
Phase 1: Parse Description
Analyze the provided description to identify:
Project Type (affects questions and scaffolding):
cli- Command-line toolwebapp- Web applicationlibrary- Reusable library/packageapi- Backend API servicedesktop- Desktop applicationmobile- Mobile applicationother- General project
Key Signals:
- "CLI", "command line", "terminal" → cli
- "web app", "website", "frontend" → webapp
- "library", "package", "SDK" → library
- "API", "backend", "service" → api
Phase 2: Interactive Discovery
Ask 3-5 targeted questions based on project type. Use AskUserQuestion tool.
Universal Questions
Always ask about:
- Target users: Who will use this? (personal, team, public)
- Scale: MVP/prototype or production-ready foundation?
Type-Specific Questions
CLI Projects:
- Target platforms? (macOS, Linux, Windows, all)
- Language preference? (Rust, Go, Python, Node.js)
- Distribution method? (Homebrew, npm, cargo, binary releases)
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.
- 8d ago First seen · 620 lines · 0 tokens per session scan A 1aae02317b4c
imagine is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,931 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.