interlinked-cli: Instructions file for Claude Code

AGENTS.md

interlinked-cli AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from QuentinCody/interlinked-cli. It costs 1,364 tokens per session, scanned A, original, MIT.

Repository-specific instructions for developing the Interlinked CLI, a TypeScript command-line tool.

In plain words
What is it for?
Use them when changing the CLI, running its build and type checks, or adding and testing commands.
Why use it?
They give coding agents the project’s file structure, commands, testing expectations, and naming conventions in one place.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: PreToolUse hook event, but also the file is AGENTS.md. Also seen: reads ~/.codex paths; mentions Codex; mentions OpenCode.

This is QuentinCody/interlinked-cli's own configuration. It tells Claude Code, Codex and OpenCode how to work on interlinked-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything interlinked-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to QuentinCody/interlinked-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/QuentinCody/interlinked-cli/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/QuentinCody/interlinked-cli

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for interlinked-cli AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/quentincody/interlinked-cli/agents-md/github.svg)](https://agentmods.dev/instructions/quentincody/interlinked-cli/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/quentincody/interlinked-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/quentincody/interlinked-cli/agents-md/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.

agentmods 80×15 button for interlinked-cli AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/quentincody/interlinked-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/quentincody/interlinked-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,364 This file is loaded in full into every session.
When invoked 1,364 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01364 $0.01364
Opus 5.5 $0.00546 $0.00546
Sonnet 5.5 $0.00273 $0.00273
Haiku 4.5 $0.00136 $0.00136

Measured 1mo ago against content hash 3f0e10fcb93f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

interlinked-cli AGENTS.md 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 1mo 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.

AGENTS.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

This package is the TypeScript source for Interlinked CLI.

  • Interlinked MCP Server refers to the remote Cloudflare Worker system that the CLI optionally talks to.
  • Interlinked CLI refers to this package.
  • src/index.ts: CLI entry point and command registration.
  • src/commands/*.ts: command handlers (enable, status, doctor, workspace, etc.).
  • src/lib/*.ts: shared logic (auth, config, hooks, API client, formatting).
  • src/templates/: generated/template assets used by setup flows.
  • src/**/*.test.ts and src/commands/__tests__/: Vitest unit/regression tests.
  • docs/architecture.md: architecture notes.
  • dist/: build output (generated).

Build, Test, and Development Commands

  • npm run dev: run the CLI directly with tsx for local development.
  • npm run build: bundle src/index.ts to dist/ with type declarations (tsup).
  • npm run typecheck: run TypeScript checks with tsgo (tsgo --noEmit).
  • npm run typecheck:stable: run the stable TypeScript compiler (tsc --noEmit).
  • npm run test: run tests once (vitest run).
  • npm run test:watch: run tests in watch mode.
  • npm run docs: regenerate generated CLI/harness reference docs.

Example:

npm run dev -- status --short

Agent Notes

  • QuentinCody/interlinked-cli is the source of truth for the CLI.
  • Keep the exact product terms distinct: Interlinked CLI is this package; Interlinked MCP Server is the remote Worker/Durable Objects system used by server-backed commands.
  • Harness phase split: PreToolUse handles deterministic pre-execution blocks and warnings (destructive commands, file reservations, secrets-in-content, grep acceleration). PostToolUse handles checks that need files on disk or project context (type/lint/security/structure), and should report only new findings through diff-aware filtering.
  • Zero-FP contract: pre_block error checks must be fully deterministic. Heuristic smell/taste/coverage checks belong as warnings or in verify --all-checks. When changing advisory policy, update DEFAULT_ADVISORY_SKIPS and its regression tests together.
  • Adding an agent-quality check usually touches src/harness/generic-checks.ts, the check registry entries, src/harness/check-metadata.ts, src/harness/check-registry/ entry files, src/commands/verify*, and parity/advisory tests. Land those coupled changes together.
  • Hook scripts generated by the CLI must stay self-contained. PostToolUse is intentionally scoped to mutating tools, and PostToolUseFailure is intentionally not registered to avoid duplicate hook-count/output issues; see docs/investigation-posttooluse-hook-count.md before changing hook matchers.
  • Rule/check metadata changes require npm run docs; do not hand-edit stale generated counts.
  • Major changes in this repository MUST include a skill-impact review. This includes user-visible CLI commands/options/output, harness behavior or policy, configuration schemas/defaults, supported-client behavior, baseline semantics, and architecture or operator workflows. Update every affected skills/*/SKILL.md in the same change; code or design-doc updates alone are not complete when agent guidance changed. If no skill is affected, state why in the final handoff.
  • Keep the skill router and focused skills aligned: update skills/interlinked/SKILL.md when a capability's routing changes, and update the relevant focused skill with the current command/config contract and operational gotchas. Treat .agents/skills/ as an installed/generated copy, not the source of truth. Validate every touched skill folder with the skill validator before handoff.
  • Supported coding clients (interlinked enable --clients <list>): claude, copilot, gemini, codex, cursor, opencode, pi. Native hook contracts live in src/harness/adapters/; legacy/per-client migration helpers live in src/lib/hook-installers*.ts; src/lib/hooks.ts is the orchestrator that wires them through CLIENT_INSTALL_REGISTRY. The generated .mjs script disambiguates Codex (Claude-shaped payloads) from Claude via the INTERLINKED_CLIENT env var set by the installed hook command. OpenCode and Pi use managed bridge files rather than the generated .mjs runtime.
  • Codex CLI hook gating: installCodexHooks writes .codex/hooks.json AND ensures [features] hooks = true in .codex/config.toml. Without that flag Codex silently ignores the hooks.json file. Uninstall leaves config.toml untouched to avoid clobbering user-managed Codex configuration.

Read the full file on GitHub · 68 lines

Changes

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.

  1. 1mo ago Changed · +41 tokens per session 3f0e10fcb93f
  2. 1mo ago First seen · 68 lines · 1,323 tokens per session scan A bef7f250e438

Subscribe to this mod's changes

interlinked-cli AGENTS.md is an instructions file published in the GitHub repository QuentinCody/interlinked-cli (180 stars, last pushed yesterday), licensed MIT. It adds 1,364 tokens to every session, about $0.0055 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-08-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens