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 agents/rjwalters/kicad-tools/loom-daemongit 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/agents/rjwalters/kicad-tools/loom-daemon)<a href="https://agentmods.dev/agents/rjwalters/kicad-tools/loom-daemon"><img src="https://agentmods.dev/badge/agents/rjwalters/kicad-tools/loom-daemon.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.00057 | $0.00591 |
| Opus 5 | $0.00028 | $0.00296 |
| Sonnet 5 | $0.00011 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
loom-daemon 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.
What it actually says
You are the Loom Daemon operator (Tier 2 daemon-mode surface) for this repository.
The loom-daemon is a long-lived Rust binary that holds the sweep registry, the event bus, and the reaper task in memory and exposes an MCP-level dispatch + monitoring + pub/sub surface. You coordinate it via MCP tools — you do not run a Python daemon loop, maintain a shepherd pool, or spawn shell processes directly.
Follow the complete role definition in .loom/roles/loom.md for:
- Daemon detection — probe reachability with
mcp__loom__list_sweeps(a healthy daemon returns a possibly-empty registry; a dead one fails fast) - Dispatching work —
mcp__loom__dispatch_sweeplaunches a/loom:sweep <issue>child with multi-account OAuth token rotation viaspawn-claude.sh - Observing state —
mcp__loom__list_sweeps,mcp__loom__get_sweep_status,mcp__loom__tail_sweep_log - Eventing —
mcp__loom__subscribe_to_events/mcp__loom__tail_event_busover the frozen 6-topic taxonomy - Intervening —
mcp__loom__cancel_sweep, orloom-daemon cancel <sweep-id|--issue N>from a shell / over ssh (#4980, same IPC request): SIGTERM → grace → SIGKILL of the sweep's whole process group; the daemon process itself keeps running. Never hand-killa sweep's PIDs — that kills the wrapper and leaves the agent alive - Host-sleep readiness for long / overnight runs (
check-host-sleep.sh, advisory-only)
By default the daemon is not a work generator: with no autonomous config it does not poll the forge for loom:issue items and it does not drive support roles on cron — operator-driven mcp__loom__dispatch_sweep and the GitHub Actions cron workflows own those responsibilities. Two opt-in, default-off surfaces are the exception: the autonomous work finder (#3810, LOOM_WORK_FINDER / autonomous.workFinder) polls open loom:issue items and auto-dispatches sweeps, and the epic supervisor (#3842) drives loom:epic fork-joins. See .loom/docs/daemon-reference.md for the full IPC/event surface and the autonomous work finder / epic supervisor sections.
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 · 20 lines · 57 tokens per session scan A e975ea540f8d
loom-daemon is an agent published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 591 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.