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-wiring-testgit 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-wiring-test)<a href="https://agentmods.dev/skills/cosmix/loom/loom-wiring-test"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-wiring-test/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-wiring-test"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-wiring-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Data Exfiltration · line 136 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.02581 |
| Opus 5 | $0.00007 | $0.01290 |
| Sonnet 5 | $0.00003 | $0.00516 |
| Haiku 4.5 | $0.00001 | $0.00258 |
Grade B, and why
loom-wiring-test scanned grade B with 2 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 6d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
- 'curl -sf -X POST localhost:8080/api/features -d ''{"name":"t"}'' | rg -q id' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
command: "curl -sf localhost:8080/health" How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiring Test Skill
Overview
Tests pass and code compiles, yet the feature is never wired up — command not registered, endpoint not mounted, module not imported, component never rendered. This is the exact failure loom's goal-backward verification exists to catch. Use this skill to write strong verification fields for a stage.
⚠️
truthsis GONE. It was removed as a standalone field. Behavioral commands now live inacceptance; the goal-backward layers areartifacts,wiring,wiring_tests,dead_code_check. Plan parsing rejectstruthsand every other unknown field, so migrate retired fields before initialization or verification.
The five verification fields
| Field | Type | Proves | Timeout |
|---|---|---|---|
acceptance |
Vec<AcceptanceCriterion> |
Build/test/lint and observable behavior | 5 min (Simple) / 30 s (Extended) |
artifacts |
Vec<String> (globs) |
Files exist with real implementation | — |
wiring |
Vec<WiringCheck> |
Static connection point present (regex in a file) | — |
wiring_tests |
Vec<WiringTest> |
Runtime integration: command output matches criteria | — |
dead_code_check |
Option<DeadCodeCheck> |
No orphaned code (see /loom-dead-code-check) |
— |
loom check <stage-id> [--suggest] runs acceptance and the goal-backward layers (artifacts, wiring, wiring_tests, dead_code_check) without changing stage state. loom stage complete also runs acceptance before transitioning the stage.
Requirement (enforced by loom init and loom plan verify): every standard and integration-verify stage must define acceptance OR at least one goal-backward check. Knowledge stages are exempt.
CRITICAL PATH RULE: all paths (artifacts, wiring.source) are relative to the stage's working_dir. working_dir: "loom" + src/x.rs → .worktrees/<stage>/loom/src/x.rs. Never ../. Double-path (loom/loom/...) is the classic mistake.
YAML WARNING: never put triple backticks inside a description field — breaks the parser (often surfaces as a misleading "missing artifacts/wiring" error). Use plain indented text.
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.
- 6d ago First seen · 218 lines · 14 tokens per session scan B 350bedc5a658
loom-wiring-test is a skill published in the GitHub repository cosmix/loom (54 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 2,581 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
press-clip
Turn a live article URL into a press clip that looks like the real coverage — the publication's own logo, fonts, photos and layout kept intact, the ads and clutter removed, and (for a roundup) just the client's section. Renders to PDF. You inspect each site and tailor the removal; the bundled script carries no…
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
coverage-tracker
Run a Google Alerts-style keyword coverage tracker. Uses news-search for recent keyword queries, lets the LLM dedupe and classify real features versus junk, stores decisions in SQLite, and alerts only on new real coverage.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
prompt-set-qa
Gate a prompt universe for schema and provenance completeness, target or campaign contamination, evidence entailment, naturalness, one-concept clarity, architecture consistency, aided status, answer leakage, and semantic duplicates. Use after realistic prompt generation and before human panel selection.
realistic-prompt-generation
Generate natural, controlled prompt variants from a target-blind design brief and prompt architecture while preserving approved jobs, acts, journeys, constraints, roles, locales, proximity bands, and evidence language. Use after architecture design and before contamination or semantic QA.