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/probe-protocolgit 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/probe-protocol)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/probe-protocol"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/probe-protocol.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.00822 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
probe-protocol 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terminal Probe Protocol (canonical)
Loom uses an intelligent probe system to detect what's running in each terminal. When you receive a probe command, respond according to this protocol.
This is the single canonical copy of the probe protocol. Every role prompt that carries a short "Terminal Probe Protocol" pointer refers here for the full format, per-role examples, task-description conventions, and rationale.
When this protocol applies (interactive terminals only)
This protocol only matters for Manual Orchestration Mode terminals —
human-launched Claude Code sessions tracked in .loom/config.json's terminals
list. Those are the only sessions a terminal probe is ever sent to.
It does not apply to:
- GitHub Actions cron one-shots (
claude -p "/<role>" --dangerously-skip-permissions) — no terminal, no probe. /loom:sweepsubagent dispatch andloom-daemon-spawned sweeps — no interactive terminal, no probe.
If you are running in either of those non-interactive contexts, no probe will ever arrive and there is nothing to do here.
When you see this probe
# Terminal Probe: Are you an AI agent? If yes, respond with "AGENT:<role>:<primary-task>". If you're a bash shell, this is just a comment.
true
How to respond
Format: AGENT:<your-role>:<brief-task-description>
Examples:
AGENT:Builder:implementing-issue-456AGENT:Judge:evaluating-PR-123AGENT:Curator:enhancing-issue-456AGENT:Champion:merging-PR-123AGENT:Doctor:fixing-changes-requested-789AGENT:Guide:triaging-issue-queueAGENT:Architect:analyzing-system-designAGENT:Hermit:scanning-for-dead-codeAGENT:Auditor:validating-main-buildAGENT:Driver:idle-awaiting-work
Role name (must be a real Loom role)
Use your assigned role name, which must be one of the roles from CLAUDE.md's "Agent Roles" table:
Builder, Judge, Champion, Curator, Architect, Hermit, Doctor,
Guide, Driver, Auditor.
Never invent a role name. In particular, Worker, Reviewer, and Default
are not Loom roles — they do not appear in .github/labels.yml,
.loom/config.json, or CLAUDE.md's role table. Use the real role name for the
prompt you are running (e.g. the Builder prompt reports AGENT:Builder:...).
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 · 80 lines · 0 tokens per session scan A bce5e19d2dc8
probe-protocol is a command published in the GitHub repository rjwalters/kicad-tools (53 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 822 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
git
Git operations with intelligent commit messages and workflow optimization.
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.