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 skills add rjwalters/kicad-tools --skill loom-curator-rate-budgetgit 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/skills/rjwalters/kicad-tools/loom-curator-rate-budget)<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/loom-curator-rate-budget"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-curator-rate-budget/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-rate-budget"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/loom-curator-rate-budget.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.00029 | $0.00570 |
| Opus 5.5 | $0.00012 | $0.00228 |
| Sonnet 5.5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
loom-curator-rate-budget 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 1mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curator: GraphQL/REST Budget (#10039)
Why curator.md's per-issue recipes are REST, and what is still unmeasured.
Why
gh issue view/edit/close are GraphQL (edit --add-label also pages the label
list). #10039 reports ~8-10 GraphQL requests per curated issue, and 8 parallel
Curators on one identity draining its pool for the hour (supplied, not
re-measured). The gate takes the min of rate_limit's core and graphql
resources: one free REST read that still sees GraphQL run out. The ~500 floor
and ~3-Curator cap are policy defaults, not vendor limits; nothing enforces the
cap across repos.
Static per-pass GraphQL cost (from the recipes, not measured)
Per claimed issue: 0 for the gate; a loom:blocked re-check adds
closedByPullRequestsReferences and a gh pr view per linked PR. Per pass:
the list query. Closes stay on gh issue close (~1 mutation each) so
guards.reversibleGh still asks; closes are rare, so the cost is negligible.
gh-cached uses gh (GraphQL) only when loom-daemon declines a read; helper
scripts' internal calls are not counted.
Measurement (close-blocking on #10039, not done)
Same identity, concurrent activity recorded: read used from both pools,
curate 15 issues, read again; repeat on a comparable batch with the old
prompt. Report deltas, commands and timestamps; if background activity cannot
be excluded, say so instead of claiming a precise saving.
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.
- 1mo ago First seen · 45 lines · 29 tokens per session scan A 9fad3e2cf50c
loom-curator-rate-budget is a skill published in the GitHub repository rjwalters/kicad-tools (73 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 570 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-10-05.
loom-curator-rate-budget compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| loom-curator-rate-budgetrjwalters/kicad-tools | Skill | 73 | yesterday | MIT | A | 29 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 2d ago | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 315k | 5d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |