agentmods.dev

add-cli-command

A guide for adding or changing commands in the installed Synergy command-line interface, including their arguments, options, aliases, help text, and exit behavior.

In plain words
What is it for?
Use it to add command groups, positional arguments, options, streaming output, confirmations, structured output, root registration, and behavior tests.
Why use it?
It helps a new command fit the existing CLI structure and connect correctly to the owning application logic. It also clarifies when a change belongs in the installed CLI versus the repository-only development tool.

Skill for Claude CodeCodex

549 3d ago A scan 60 tokens original MIT
View the source file SII-Holos/synergy
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.

agentmods
npx agentmods add skills/sii-holos/synergy/add-cli-command
Any agent
npx skills add SII-Holos/synergy --skill add-cli-command
Clone the repo
git clone --depth 1 https://github.com/SII-Holos/synergy

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 738 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00060 $0.00738
Opus 5 $0.00030 $0.00369
Sonnet 5 $0.00012 $0.00148
Haiku 4.5 $0.00006 $0.00074

Measured 3d ago against content hash a7ab459e2564, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-cli-command 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 3d 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.

.synergy/skill/add-cli-command/SKILL.md · 53 lines

How it starts

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

Add a CLI Command

Discover the Contract

  1. Read CLI reference and inspect packages/synergy/src/index.ts.
  2. Locate the nearest command with the same shape: local operation, server-attached operation, nested command group, streaming output, or destructive confirmation.
  3. Decide whether the behavior belongs in the installed synergy CLI or the source-only bun dev orchestrator. Edit script/dev.ts only for the latter.

Implement

  1. Write a failing behavior test first when adding behavior or fixing a bug.
  2. Add or update a named command in packages/synergy/src/cli/cmd/ with cmd(). Match neighboring yargs builder, positional, alias, and output patterns rather than imposing a parallel style.
  3. Keep domain logic in its owning module. Let the command parse input, establish Scope or server attachment, call the domain API, format output, and set an appropriate exit status.
  4. Give every command, positional, and option useful help text. Support structured output when the adjacent command family already does.
  5. Register a root command in packages/synergy/src/index.ts; register a nested command in its owning command-group builder.
  6. Use generated SDK/server helpers for attached commands where the family already does. Preserve auth, directory/Scope, timeout, and error semantics.
  7. Regenerate the SDK with ./script/generate.ts only if an API route or OpenAPI-visible schema changed.

Command Contract

  1. Separate the command kinds: discovery commands (list accounts, projects, or queues), resolve commands (name or URL to a stable ID), read commands (exact object fetch plus a bounded list/search with --limit or a cursor), and narrow write commands (one named action each; prefer --dry-run or draft mode when the service allows).
  2. When the neighboring command family already supports structured output, support stable --json output with a documented success shape and machine-readable errors. Never include credentials in error output.
  3. Write self-explanatory help text: every command, positional, and option describes its purpose, and --help surfaces every major capability.
  4. Keep a raw escape hatch only where the family needs one. Never expose only a generic raw request command without high-level verbs.

Read the full file on GitHub · 53 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. 3d ago First seen · 53 lines · 60 tokens per session scan A a7ab459e2564

Subscribe to this mod's changes

add-cli-command is a skill published in the GitHub repository SII-Holos/synergy (549 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 738 once invoked, about $0.0003 per session on Opus 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens