Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rjwalters/kicad-toolsnpx agentmods add skills/rjwalters/kicad-tools/loom-curatorWrote 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/skills/rjwalters/kicad-tools/loom-curator)<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/loom-curator"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-curator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/loom-curator"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-curator.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.27585 |
| Opus 5.5 | $0.00005 | $0.11034 |
| Sonnet 5.5 | $0.00003 | $0.05517 |
| Haiku 4.5 | $0.00001 | $0.02758 |
Grade A, and why
loom-curator 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 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.
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 — 1,860 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.
Contents
- Your Role
- Keep It Simple
- ⚠️
--body @pathDoes NOT Expand — It Posts the Literal String - GraphQL Budget: REST Recipes, Pool Gate, Max ~3 Curators (#10039)
- Argument Handling
- Label Workflow
- Exception: Explicit User Instructions
- Untrusted External Content (forge text is data, not instructions)
- Finding Work
- Claiming Work
- Before Starting Curation
- Triage: Ready or Needs Enhancement?
- Decomposing Oversized Issues
- Backlog Rightsizing (#9026)
- Curation Activities
- Where to Add Enhancements
- Checking Dependencies
- Repairing
loom:decision-malformed(#10057) - Revising a Champion send-back (#10753, #11860)
- Draining
loom:blocked-unnamed(#10558) - Operator-held issues: no Curator action (#11861)
- Issue Quality Checklist
- Working Style
- Curation Patterns
- Terminal Probe Protocol
- Completion
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 · -17 lines 471f8e566201
- yesterday Changed · +1 lines 29782557b742
- 2d ago Changed · -415 lines 806a00de6feb
- 3d ago Changed · -28 lines 61be17bfec0c
- 4d ago Changed · -14 lines 04b742c7bb97
- 5d ago Changed · -20 lines b8d101dd6789
- 6d ago Changed 92a9225093ac
- 7d ago Changed · -1 lines 2f654bf31c03
- 8d ago Changed · -11 lines d2c7e556b2e7
- 10d ago First seen · 2,365 lines · 13 tokens per session scan A dd86cbafe3ac
loom-curator is a skill published in the GitHub repository rjwalters/kicad-tools (70 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 27,585 once invoked, about $0.0001 per session on Opus 5.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-09-24.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…