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-verifygit 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-verify)<a href="https://agentmods.dev/skills/quentincody/interlinked-cli/interlinked-verify"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-verify/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-verify"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00157 | $0.25039 |
| Opus 5.5 | $0.00063 | $0.10016 |
| Sonnet 5.5 | $0.00031 | $0.05008 |
| Haiku 4.5 | $0.00016 | $0.02504 |
Grade A, and why
interlinked-verify 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`readFileSync`, `existsSync`, `stat`, a namespace or default `fs` import; `child_process`, How it starts
The opening of the file, as written. The whole thing — 1,546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interlinked-verify — check your work & land edits through the gates
The experimental metrics decisions pipeline is separate from verify and its
check registry. Its opt-in PostToolUse warnings are advisory, use actual pre-edit
hashes, and retain failures/budget exclusions as unmeasured outcomes. They do not
clear type, coverage, mutation or e2e obligations and do not change
DEFAULT_ADVISORY_SKIPS. Use interlinked-quality-gates and
docs/decision-metrics.md for pilot labels, five-arm audits and model drift.
Claude compiler batches
After a Claude session has delivered a native PostToolBatch, declared single-file
edits queue TypeScript checking until that boundary. Related edits in the same model
message are checked against the completed tree, once per project. Existing atomic
multi-file calls retain their shared check path. Other clients, unknown writers, and
Claude sessions that have not demonstrated the boundary keep per-edit checking.
Security, content guards and lint still apply per edit. Function-token and
complexity caps advise by default; harness.edit_metrics.mode: "enforced"
opts into their existing hard edit gate without changing limits or baselines.
Deep-audit findings follow DEFAULT_ADVISORY_SKIPS in ordinary hook feedback as
well as default verify. Run verify --all-checks for the full review; raw findings
remain in check-results.jsonl. Repeated warnings never gain severity or confidence
from repetition. Project-wide Gitleaks runs in explicit verify/background recovery,
not the interactive ChangeSet batch. Inline secret checks remain active. A deferred
Gitleaks scan is NOT CHECKED, never a passing security verdict.
Final compiler errors arrive as batch context so Claude can repair them; a native batch
block would cancel its loop. Unresolved errors and unavailable compiler work remain
in .interlinked/compiler-batches/ and are checked before Stop and commit, including
after daemon restart. Do not delete this state to bypass verification. A queued edit
has no TypeScript verdict and must not be described as fully checked. Explicit verify
and commit checks remain necessary for the required repository validation scope.
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 · +57 lines 665a9be9e540
- 7d ago Changed · +221 lines 9e8cbafee8ef
- 24d ago Changed · +154 lines 35008c40de76
- 28d ago Changed · +68 lines eacb64d7a21d
- 1mo ago Changed · +150 lines 734e43abbe47
- 1mo ago Changed · +58 lines 2e9b9cd9f138
- 1mo ago Changed · +143 lines cd73de9b343a
- 1mo ago Changed · +33 lines 64feb340b27f
- 1mo ago Changed · +363 lines ddc8642630a4
- 1mo ago First seen · 299 lines · 157 tokens per session scan A 778159b9bea8
interlinked-verify is a skill published in the GitHub repository QuentinCody/interlinked-cli (180 stars, last pushed yesterday), licensed MIT. It adds 157 tokens to every session and 25,039 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.