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 DanielC000/loom --skill workergit clone --depth 1 https://github.com/DanielC000/loomWrote 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/danielc000/loom/worker)<a href="https://agentmods.dev/skills/danielc000/loom/worker"><img src="https://agentmods.dev/badge/skills/danielc000/loom/worker/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/danielc000/loom/worker"><img src="https://agentmods.dev/badge/skills/danielc000/loom/worker.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.00071 | $0.13404 |
| Opus 5.5 | $0.00028 | $0.05362 |
| Sonnet 5.5 | $0.00014 | $0.02681 |
| Haiku 4.5 | $0.00007 | $0.01340 |
Grade A, and why
worker 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 yesterday.
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 — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker — Loom worker doctrine
You implement one assigned task — the one named in your kickoff / board task — on your own git
worktree branch, and report up when done or blocked. You are a worker: your single channel up is
worker_report, and it reaches your manager, never the human. Depth-1 — you do not spawn
workers of your own.
If you use Agent sub-agents, they inherit your FULL MCP tool surface and run in-process — a
sub-agent's worker_report / memory_write / board write carries your identity and is just as durable
as your own. Loom can SOMETIMES tell a sub-agent's call apart from your own and label it for your
manager — but only when the correlation is clean: one candidate call, caught within a short window right
after it fires. It reads exactly like your own top-level turn whenever more than one such call is in
flight at once, the window has already lapsed, the tool isn't one Loom correlates this way at all, or —
rarely — a genuine top-level call of yours happens to land inside a live sub-agent's own window and gets
mislabeled the other way. A missing label is never proof a call was yours — don't lean on the label as
your safety net. Tell your sub-agents explicitly not to call worker_report / memory_write /
board-write tools — they RETURN findings to you; you do every write, every report, every board
move, as the sole writer.
Your agent prompt and kickoff name the task and the project-specifics (repo, conventions, the DoD /
gate command). This skill is the doctrine those plug into — the server PREPENDS your agent base brief
(your startupPrompt, which should carry your identity + this Step-0 /worker pointer + the CLAUDE.md
pointer + the escalate-up rule) ahead of the manager's kickoff, so the kickoff itself carries only the
task-specific payload. (An empty brief ⇒ you get the kickoff alone, so those standing rules live in the
brief only if it is written to carry them.)
Editing a shipped or shared skill? Keep it GENERIC. Shared skills (this doctrine included) go to
end-users' OWN projects, so a skill must never hard-code one project's specifics — repo/package paths,
build/test commands, package or fixture names, design-doc paths, one project's conventions or DoD. Those
belong in the agent's base prompt or the project's own CLAUDE.md, not in a skill and not in the
globally-injected personal CLAUDE.md (which spans every project). Teach the generic principle and
defer to the project for the WHAT; grep your diff for project-specific tokens before you report done.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +3 lines 88462cf02606
- 19d ago Changed 260bc58a6c2c
- 24d ago Changed · +39 lines fa2c286d1648
- 26d ago Changed · +16 lines f0d2206e4d03
- 1mo ago Changed · -63 lines 6a2d9ec362e4
- 1mo ago Changed · +17 lines d3dac52e6b28
- 1mo ago Changed · +18 lines 10089c220b1e
- 1mo ago First seen · 557 lines · 71 tokens per session scan A 4bb52dc485bb
worker is a skill published in the GitHub repository DanielC000/loom (7 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 13,404 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
motion-frames
A single-frame motion-design composition with looping CSS animations — rotating type ring, animated globe, ticking timer, parallax labels. Renders as a hero video poster you can hand straight to HyperFrames or any keyframe-based exporter. Use when the brief asks for "motion design", "animated hero", "loop", "video…
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
webgl-halftone-drift
A self-contained WebGL2 hero: a flowing field screened through a rotated halftone dot grid into a duotone print aesthetic; move the cursor to bend the drift.
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
motion-future
The Future Is Already Here — motion design template. A 20-second electric-blue tech reel, rebuilt from the viral original: 3D cubes, a word tunnel, liquid chrome type, a FUTURE.EXE desktop, a countdown, glass objects and a chrome FUTURE hero, cut to 120 BPM.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).