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 loom-task-startgit 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/loom-task-start)<a href="https://agentmods.dev/skills/danielc000/loom/loom-task-start"><img src="https://agentmods.dev/badge/skills/danielc000/loom/loom-task-start/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/loom-task-start"><img src="https://agentmods.dev/badge/skills/danielc000/loom/loom-task-start.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.00068 | $0.00477 |
| Opus 5.5 | $0.00027 | $0.00191 |
| Sonnet 5.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 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.
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.
- 1mo 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 yesterday), licensed MIT. It adds 68 tokens to every session and 477 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
orbit-linear
Open Orbit briefing skill — selected by the Orbit pipeline when Linear is the user's only connected connector, or when the user explicitly scopes their daily digest to Linear. Pulls the past 24 hours of issue movement, status changes, assignments, and cycle progress from the user's authenticated Linear connection and…
flowai-live-dashboard-template
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity sparklines, and a top-contributors panel, all in a single self-contained HTML file with light/dark theming, hoverable…
code-import
Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
kanban-board
Kanban / task board with columns (To do / In progress / In review / Done), draggable-looking cards, assignee avatars, swimlanes, and a top filter bar. Use when the brief mentions "kanban", "task board", "sprint board", "trello", "看板".
meeting-notes
A meeting-notes page with attendees, an agenda checklist, decisions, action items, owners, due dates, open questions, and the next meeting.
pm-spec
A product-specification page skill for documenting a feature's problem, goals, user stories, success measures, rollout plan, and open questions. A PRD is a document that explains what a product feature should achieve and why.