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 QuentinCody/interlinked-cli --skill interlinked-spec-auditgit clone --depth 1 https://github.com/QuentinCody/interlinked-cliWrote 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/quentincody/interlinked-cli/interlinked-spec-audit)<a href="https://agentmods.dev/skills/quentincody/interlinked-cli/interlinked-spec-audit"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-spec-audit/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/quentincody/interlinked-cli/interlinked-spec-audit"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-spec-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Prompt Injection · line 13 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.
- medium Rogue Agent · line 3 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.00163 | $0.03215 |
| Opus 5.5 | $0.00065 | $0.01286 |
| Sonnet 5.5 | $0.00033 | $0.00643 |
| Haiku 4.5 | $0.00016 | $0.00321 |
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 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.
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 — 205 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.
- today Changed · +7 lines 5df94532754f
- 1mo ago Changed · +8 lines a4c92524544a
- 1mo ago Changed · +41 lines 5ad6edf3f0b7
- 1mo 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 (180 stars, last pushed yesterday), licensed MIT. It adds 163 tokens to every session and 3,215 once invoked, about $0.0007 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.