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 cosmix/loom --skill loom-plan-writergit clone --depth 1 https://github.com/cosmix/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/cosmix/loom/loom-plan-writer)<a href="https://agentmods.dev/skills/cosmix/loom/loom-plan-writer"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-plan-writer/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/cosmix/loom/loom-plan-writer"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-plan-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 148 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Prompt Injection · line 214 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 772 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Privilege Escalation · line 838 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 8 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 390 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 608 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 830 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00014 | $0.09978 |
| Opus 5.5 | $0.00006 | $0.03991 |
| Sonnet 5.5 | $0.00003 | $0.01996 |
| Haiku 4.5 | $0.00001 | $0.00998 |
Grade A, and why
loom-plan-writer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Warnings: a network binary in a criterion (`curl`, `wget`, `gh`, `npm install`, `bun install`, `cargo install`, `cargo audit` without `--no-fetch`); a read of a `doc/plans/` path, which the plan lifecycle renames; `vit How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loom Plan Writer
THE REQUIRED SKILL FOR CREATING LOOM EXECUTION PLANS. Invoke it whenever an agent needs to author a plan for loom orchestration.
A loom plan is a DAG of stages loom runs in isolated git worktrees, parallel first through subagents within a stage, second through concurrent stages. It is only as good as its CLAIMS about the code are TRUE and its verification PROVES them.
Where other doctrine already governs something, this skill points at it: subagent shapes, preambles and waiting live in the loom-orchestration skill (## Rule 6 — Subagents, ## Rule 7 — Model allocation; the subagent preamble itself is loom-hooks/_subagent-preamble.txt, CLAUDE.md Rule 5); memory routing and branch discipline in CLAUDE.md Rules 12, 18 and 9b.
Two rules dominate everything below:
- Ground every claim before you write it (Section 1) — the #1 cause of bad plans.
- The plan file is your deliverable. After writing it, STOP (Section 2) — never implement.
References — detail moved out of this file. Read one when its note applies:
| File | Read when |
|---|---|
references/grounding-protocols.md |
A stage widens a shared type, reuses or mirrors code, adds a destructive path, runs code under a new runtime, or depends on a sibling plan |
references/bookend-stages.md |
Writing a bookend stage and Section 3's short forms leave a question open |
references/stage-sizing.md |
Sizing workers, subagent_timeout_secs, or writing a description an orchestrator decomposes |
references/codex-implementers.md |
Choosing each stage's implementation lanes (codex, Claude, or both), or a stage lists codex in implementers |
references/parallelization.md |
More than about six workers, an agent team, or an ultracode stage |
references/verification-rules.md |
Writing any acceptance or wiring_tests entry, or a criterion about an artifact the stage will produce |
references/sandbox.md |
Configuring sandbox, or a criterion writes files or needs a host resource, network, or HOME |
references/authoring-detail.md |
A short form in Sections 2, 4, 5, 6, 7 or 9 leaves a question open |
references/plan-template.md |
Writing plan YAML: canonical structure, bookends and one implementation stage |
references/v2-contracts.md |
Writing a version: 2 plan: contracts, harness, reachable, ratchet files, the review gate |
What ships with it
10 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.
- references/authoring-detail.md 17 KB
- references/bookend-stages.md 8.3 KB
- references/codex-implementers.md 14 KB
- references/grounding-protocols.md 21 KB
- references/parallelization.md 7.7 KB
- references/plan-template.md 9.3 KB
- references/sandbox.md 14 KB
- references/stage-sizing.md 9.4 KB
- references/v2-contracts.md 23 KB
- references/verification-rules.md 14 KB
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 1af4c09de95c
- yesterday Changed 2bcfc38ad327
- 5d ago Changed 2e13133f4a6b
- 7d ago Changed · -330 lines ac5ee3053bea
- 9d ago Changed · +2 lines bc73fd3757a4
- 10d ago Changed 070d74c0e1d1
- 16d ago Changed · +7 lines b8f0323caf24
- 20d ago Changed e2eecdbcc26b
- 22d ago Changed · +30 lines a3422ad48c93
- 25d ago First seen · 677 lines · 14 tokens per session scan A 5e99f8b4fa3e
loom-plan-writer is a skill published in the GitHub repository cosmix/loom (63 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 9,978 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
publish-vscode-extension
Publish a VS Code extension to the VS Code Marketplace and/or Open VSX Registry. Use when the user wants to publish, ship, or release a VS Code extension; audit or improve manifest, listing, or release setup; build or upload a .vsix; set up vsce or ovsx; create a marketplace publisher or Open VSX namespace; configure…
skill-upstream-pr
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-creator's retrofit, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
meanest-editor
Roast a pitch or press release with the eye of a veteran PR director. Honest, sharp, constructive — never cruel for its own sake.
headline-generator
Generate headline candidates from a story's raw facts: news-style headlines, press-release headlines, and pitch subject lines. A pure generation skill — it finds the charge in the facts, then runs ten proven moves (consequence, picture, number-as-hero, two-beat turn, naming, reader's-own-story, open question, voice…
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…
docs-updater
Provides automated documentation updates by analyzing git changes between the current branch and the last release tag. Performs git diff analysis to identify modifications, then updates README.md, CHANGELOG.md following Keep a Changelog standard, and discovers documentation folders for contextual updates. Use when…