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 skills/danielc000/loom/loom-task-startnpx skills add DanielC000/loom --skill loom-task-startgit clone --depth 1 https://github.com/DanielC000/loomWhat 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.00068 | $0.00477 |
| Opus 5 | $0.00034 | $0.00238 |
| Sonnet 5 | $0.00014 | $0.00095 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
loom-task-start 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 3d 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.
What it actually says
Task Start (Loom)
Make the work trackable on the board before diving in. The board is the source of truth — one task = one focused, independently-mergeable change.
Steps
- Find or create the task —
tasks_list(theloom-tasksMCP); if none matches,tasks_createwith a clear, specific title in Conventional-Commits form (type(scope): summary— lowercase type likefeat/fix/refactor, imperative summary), drawing the scope from the project'sCLAUDE.md"Commit scopes". - Scope it. Put the scope and a sharp definition of done in the task body (
tasks_updatebody). The DoD states what proves it works — a command that exits clean, a manual repro, a regression check. A task without a DoD isn't ready to work. If an open decision blocks pinning the DoD, ask the human viaquestion_ask(the Requests inbox) rather than guessing. Keep it to one logical change; if it's really several, split it. - Move it — set the task to the
activecolumn (the in-progress ROLE) viatasks_updatecolumnKey. First, skip any card flaggedheld(an owner brake) ordeferred(the manager hasn't sequenced it) — don't begin work on those. - Load context before changing anything —
git log --oneline -15, readCLAUDE.md, and read the relevant code/notes so your change matches what's there. Reuse existing shapes over inventing new ones.
Then implement: keep the change small and matched to the surrounding code, meet the DoD, and build/ verify before reporting it done.
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.
- 3d ago First seen · 31 lines · 68 tokens per session scan A a3af06f03ae4
loom-task-start is a skill published in the GitHub repository DanielC000/loom (7 stars, last pushed 7d ago), licensed MIT. It adds 68 tokens to every session and 477 once invoked, about $0.0003 per session on Opus 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
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 "入职".
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).
new-changelog
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under packages/changelog/content. Use this when the task is specifically about determining the next version and creating the markdown entry.
self-awareness
Inspect Open Science's JavaScript control REPL, discover managed Project files, Sessions, and Agent Frames, and safely feature-gate host. calls with host.capabilities(). Use when an Agent needs to discover available host APIs, locate an Artifact or Upload Version, diagnose a Session, or read a Frame transcript in the…
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.
guideline-learning-diagnosis
当用户要求评估自己对某份指南的掌握情况、制定指南学习/备考计划、梳理薄弱章节、 做教育性小测，或学习指南中的诊断标准、鉴别框架和流程关系时使用。 本技能只做学习诊断与诊断标准教学，不对具体患者作疾病诊断、治疗、处方、剂量、 急诊处置或医保报销判断。.