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/quentincody/interlinked-cli/interlinked-spec-auditnpx skills add QuentinCody/interlinked-cli --skill interlinked-spec-auditgit clone --depth 1 https://github.com/QuentinCody/interlinked-cliWhat 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.00163 | $0.02402 |
| Opus 5 | $0.00081 | $0.01201 |
| Sonnet 5 | $0.00033 | $0.00480 |
| Haiku 4.5 | $0.00016 | $0.00240 |
Grade B, and why
interlinked-spec-audit scanned grade B 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 2d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
exits 0. Only tagged fences run (untagged `rm -rf` examples are never executed). Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interlinked-spec-audit — keep prose specs honest against code
The spec-audit system is three cooperating substrates plus doctest. Its one policy: detect, never autofix — findings carry evidence and candidate resolutions, but the agent always writes the fix.
- Fact ledger (
interlinked spec) — deterministically extracts the enumerable facts that drift during revision (ID registries likeFG-INV-07/B7, count/range claims, headings/§-refs, backticked paths,<!-- fact:NAME -->markers), merges them cross-file, and flags disagreements ("drift") at edit time. - Findings reconciliation (
interlinked findings) — ingest an external reviewer's numbered report into a durable corpus, then track each finding to closure (touched by an overlapping edit, or acked with a reason). - Invariants + review agenda — extract a doc's invariants into a taxonomy, and generate a standing discovery agenda for the next reviewer.
Load this when
- Extracting invariants/facts from a design doc, or building a review agenda.
- You see a
[interlinked:spec-*]or[interlinked:disputed-ground]warning after a markdown edit. - Ingesting or triaging an external code-review report.
- Running executable examples embedded in docs.
interlinked spec
Two subcommands, no flags:
interlinked spec agenda # → .interlinked/review-agenda.md
interlinked spec invariants <file> # → .interlinked/policies/<basename>.invariants.md
spec agenda— walks cwd, writes a review agenda with three sections: compose-checks (an ID namespace/declared fact constrained from ≥2 files — "read them together, confirm no contradiction"), coverage gaps (a section whose heading matches a kind — format / protocol / crypto-keys / … — but whose body omits that kind's standard concerns), and outstanding deterministic drift, then an open review-findings section appended last. It asks questions, never renders verdicts.spec invariants <file>— for markdown: numbered registry rows + MUST/never/"sole truth" doctrine sentences (fenced code/blockquotes skipped). For code:// INVARIANT:/// SAFETY:comments +assert(/assert!calls. Output is a labeled taxonomy with verbatim quotes +file:lineprovenance (review context / Tier-2 classification input).
What ships with it
1 file 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.
- 2d ago First seen · 149 lines · 163 tokens per session scan B 95ec10429dba
interlinked-spec-audit is a skill published in the GitHub repository QuentinCody/interlinked-cli (13 stars, last pushed 15d ago), licensed MIT. It adds 163 tokens to every session and 2,402 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…