A checklist for connecting new command files to a command-line application's main entry point and help text.

Use it when adding or reviewing commands in the Squad CLI, including argument parsing, command routing, and help output.

It prevents commands from being written but remaining unreachable because the application never routes to them or documents their usage.

cli-wiring — Skill for Claude Code and Codex by alonf/specrew

Install

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.

Any agent

npx skills add alonf/specrew --skill cli-wiring

Clone the repo

git clone --depth 1 https://github.com/alonf/specrew

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alonf/specrew/cli-wiring/github.svg)](https://agentmods.dev/skills/alonf/specrew/cli-wiring)

Your own site

<a href="https://agentmods.dev/skills/alonf/specrew/cli-wiring"><img src="https://agentmods.dev/badge/skills/alonf/specrew/cli-wiring/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alonf/specrew/cli-wiring"><img src="https://agentmods.dev/badge/skills/alonf/specrew/cli-wiring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 481 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00481
Opus 5.5	$0.00000	$0.00192
Sonnet 5.5	$0.00000	$0.00096
Haiku 4.5	$0.00000	$0.00048

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

Security

Grade A, and why

cli-wiring 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.

Origin

This is a copy

91% identical to cli-wiring — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.copilot/skills/cli-wiring/SKILL.md · 48 lines

What it actually says

Skill: CLI Command Wiring

Bug class: Commands implemented in packages/squad-cli/src/cli/commands/ but never routed in cli-entry.ts.

Checklist — Adding a New CLI Command

Create command file in packages/squad-cli/src/cli/commands/<name>.ts
- Export a run<Name>(cwd, options) async function (or class with static methods for utility modules)

Add routing block in packages/squad-cli/src/cli-entry.ts inside main():

if (cmd === '<name>') {
  const { run<Name> } = await import('./cli/commands/<name>.js');
  // parse args, call function
  await run<Name>(process.cwd(), options);
  return;
}

Add help text in the help section of cli-entry.ts (search for Commands:):

console.log(`  ${BOLD}<name>${RESET}     <description>`);
console.log(`             Usage: <name> [flags]`);

Verify both exist — the recurring bug is doing step 1 but missing steps 2-3.

Wiring Patterns by Command Type

Type	Example	How to wire
Standard command	`export.ts`, `build.ts`	`run*()` function, parse flags from `args`
Placeholder command	`loop`, `hire`	Inline in cli-entry.ts, prints pending message
Utility/check module	`rc-tunnel.ts`, `copilot-bridge.ts`	Wire as diagnostic check (e.g., `isDevtunnelAvailable()`)
Subcommand of another	`init-remote.ts`	Already used inside parent + standalone alias

Common Import Pattern

import { BOLD, RESET, DIM, RED, GREEN, YELLOW } from './cli/core/output.js';

Use dynamic await import() for command modules to keep startup fast (lazy loading).

History

#237 / PR #244: 4 commands wired (rc, copilot-bridge, init-remote, rc-tunnel). aspire, link, loop, hire were already present.

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.

1mo ago First seen · 48 lines · 0 tokens per session scan A 931fdb23ad9c

Subscribe to this mod's changes

cli-wiring is a skill published in the GitHub repository alonf/specrew (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 481 tokens. A static security scan graded it A with 0 findings. It is 91% identical to cli-wiring, differing in 4 lines, and is treated as a copy.

Debugging

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens