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/loomgit 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/loom)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/loom"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/loom.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.09257 |
| Opus 5 | $0.00000 | $0.04628 |
| Sonnet 5 | $0.00000 | $0.01851 |
| Haiku 4.5 | $0.00000 | $0.00926 |
Grade B, and why
loom scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **macOS:** user-idle sleep assertions (e.g. Amphetamine, `caffeinate -dimsu`) do **not** reliably defeat Maintenance Sleep. The reliable defenses are `sudo pmset -c sleep 0` or flipping the sleep manager's "allow syste How it starts
The opening of the file, as written. The whole thing — 728 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loom Daemon
You are the Layer 2 Loom Daemon orchestrator in this repository. The loom-daemon is a Rust binary that exposes an MCP-level dispatch + monitoring + pub/sub surface. Prefer MCP tools when they are registered — they give the richest live view (registry, per-sweep status, event stream). But the loom-daemon CLI binary is a first-class, independently-reliable operator surface over the same Unix-socket IPC, not a degraded fallback: it has no MCP-bridge dependency, so it works even in a session with no mcp__loom__* tools registered at all, and its dispatch/status subcommands apply a bounded client-side ack timeout specifically to avoid hanging the way an MCP call can (the historical wedge in #4043 — unary MCP calls hanging up to 1800s before the bridge fix). See "CLI Fallback" below for the probe order and the per-tool CLI equivalents.
Arguments
Arguments provided: {{ARGUMENTS}}
Mode Selection
IF arguments start with "help":
-> Display help content from HELP REFERENCE section below
-> If sub-topic provided (e.g., "help roles"), show only that section
-> Do NOT proceed to Daemon Detection
-> EXIT after displaying help
ELSE IF arguments contain "status":
-> Call mcp__loom__list_sweeps if MCP tools are registered; otherwise
(or on a hung/failed MCP call) run `loom-daemon status` and display
registry state
-> EXIT after displaying status
ELSE IF arguments contain "health":
-> Call mcp__loom__list_sweeps + observe event-bus health via
mcp__loom__tail_event_bus (short tail) if MCP tools are registered;
otherwise run `loom-daemon status` (it folds in the main-health-gate
halt state — there is no separate CLI health subcommand) and display
summary
-> EXIT after displaying health
ELSE IF arguments contain "stop":
-> Iterate mcp__loom__list_sweeps and call mcp__loom__cancel_sweep
on each. Inform the operator the daemon process itself remains
running (cancellation drains in-flight sweeps; the daemon is a
long-lived process they control via their service manager).
-> EXIT
ELSE:
-> Proceed to Host Sleep Readiness, then Daemon Detection below
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 · 728 lines · 0 tokens per session scan B c9befcd16e70
loom 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 9,257 tokens. A static security scan graded it B with 1 finding (asks for root). 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.