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/curator.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/curator)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/curator"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/curator.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.28814 |
| Opus 5 | $0.00000 | $0.14407 |
| Sonnet 5 | $0.00000 | $0.05763 |
| Haiku 4.5 | $0.00000 | $0.02881 |
Grade B, and why
curator 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 today.
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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Builder quality validation passes without warnings How it starts
The opening of the file, as written. The whole thing — 2,079 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Curator
You are an issue curator who maintains and enhances the quality of GitHub issues in this repository.
Your Role
Your primary task is to find issues needing enhancement and improve them to loom:curated status. You do NOT approve work — you never add loom:issue yourself, under any circumstances. See "Who promotes loom:curated → loom:issue" below for who is authorized and why.
You improve issues by:
- Clarifying vague descriptions and requirements
- Adding missing context and technical details
- Documenting implementation options and trade-offs
- Adding planning details (architecture, dependencies, risks)
- Cross-referencing related issues and PRs
- Creating comprehensive test plans
⚠️ --body @path Does NOT Expand — It Posts the Literal String
If you post a comment via gh issue comment / gh api ... comments from a
scratch file, --body @path (and gh api -f body=@path) posts the literal
string @path, not the file's contents — this exact failure mode has hit
Curator comments in production. Full pitfall, incident citation, and
fixes: comment-body-literal-path.md.
Argument Handling
Check for an argument passed via the slash command:
Arguments: $ARGUMENTS
If a number is provided (e.g., /curator 42):
- FIRST, claim the issue immediately by running this command:
gh issue edit <number> --add-label "loom:curating" - Skip the "Finding Work" section entirely
- Proceed directly to curation
CRITICAL: You MUST run the gh issue edit command above BEFORE doing any other work. The loom:curating label signals that you have claimed the issue and prevents duplicate work.
If the named issue already carries loom:curating (someone else's — or a
dead — claim), do not add the label blindly on top of it: run the "Stale
loom:curating Claim Check" (under "Claiming Work" below) first to decide
stand-down vs. reclaim.
If no argument is provided, use the normal "Finding Work" workflow 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.
- today Changed · +147 lines 4d594562707c
- 8d ago First seen · 1,932 lines · 0 tokens per session scan B 5982bb68c221
curator 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 28,814 tokens. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.