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-simplificationgit 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-simplification)<a href="https://agentmods.dev/skills/quentincody/interlinked-cli/interlinked-simplification"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-simplification/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-simplification"><img src="https://agentmods.dev/badge/skills/quentincody/interlinked-cli/interlinked-simplification.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.00099 | $0.02284 |
| Opus 5.5 | $0.00040 | $0.00914 |
| Sonnet 5.5 | $0.00020 | $0.00457 |
| Haiku 4.5 | $0.00010 | $0.00228 |
Grade A, and why
interlinked-simplification scanned grade A with 0 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 28d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interlinked-simplification — evidence before removal
Interlinked's simplification surface finds code that may be unnecessary without treating static
signals as permission to delete it. Local analysis is deterministic, offline, advisory, and does
not invoke an LLM or apply a fix. The only optional write, --record, stores findings metadata;
it never edits source or changes the branch.
Choose the scope
For dense JS/TS, interlinked metrics expressions <path> --json supplies advisory
locations and measurements. A smaller function or lower branch count is not a complete
review. Name domain concepts while preserving the context their decisions require;
explicit iteration and compact named pipelines can both be appropriate. Review whether
dependent checks reuse the same prerequisite observation, distinguish failure from
not-evaluated, and make success claims only about what was established. Preserve command
origin, suite and execution phase until availability decisions are complete. Validate
relevant failure cases from the requirement; these questions are semantic review guidance,
not static proofs or new automatic blockers. See interlinked-quality-gates for budgets.
| Command | Scope and effect |
|---|---|
interlinked simplify scan [--cwd <path>] [--json] [--record] |
Run the deterministic repository scan. |
interlinked simplify review [--changed|--staged|--range <base..head>] [--deep-handoff] [--json] [--record] |
Emit findings for one git-selected path set while retaining whole-repo context. --changed is the default; the three selectors are mutually exclusive. |
interlinked simplify audit [--deep-handoff] [--json] [--record] |
Run the deterministic repository audit. --deep-handoff embeds a portable Agent CI request but does not submit it. |
interlinked simplify status [--cwd <path>] [--json] |
Read locally recorded run receipts and their materialized common-corpus findings. No network. |
simplify audit is intentionally distinct from top-level interlinked audit verify, which
checks the tamper-evident guard-decision chain. It is also distinct from interlinked debt,
whose list, show, and resolve verbs operate the automatic obligation ledger.
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.
- 28d ago Changed · +10 lines a2a56fa82e46
- 1mo ago Changed · +21 lines b116dc97e994
- 1mo ago Changed · +15 lines b86721d2b5f4
- 1mo ago First seen · 112 lines · 99 tokens per session scan A 8092c050fa23
interlinked-simplification is a skill published in the GitHub repository QuentinCody/interlinked-cli (180 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 2,284 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
sync-model-processor
Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.