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 agentmods add skills/harshanandak/forge/command-surfacenpx skills add harshanandak/forge --skill command-surfacegit clone --depth 1 https://github.com/harshanandak/forgeWhat 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 | $0.00054 | $0.00661 |
| Opus 5 | $0.00027 | $0.00331 |
| Sonnet 5 | $0.00011 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
command-surface 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 2d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
command-surface
A command file is five surfaces, not one. Add the file and stop, and the compiled binary breaks while dev-mode auto-discovery hides it from you.
The surfaces
Adding, renaming, or removing lib/commands/<name>.js means all of these:
-
Manifest — regenerate the static require graph:
node scripts/gen-command-manifest.js # write if changed node scripts/gen-command-manifest.js --check # exit 1 if stalelib/commands/_manifest.jsis generated; never hand-edit it. Drift is enforced bytest/structural/command-manifest-drift.test.js. [verified 2026-08-13] -
Registry — the command must resolve through the CLI registry (
test/forge-cli-registry.test.js,test/cli-flags.test.js). -
Skill coverage —
skills/coverage.jsonmaps every registered user-facing command to an owning skill, or carries an explicit{ exempt: <reason> }. Enforced byevaluateCoverageinlib/skill-eval.jsand gated intest/skill-eval.test.js. [verified 2026-08-13] -
Test lane — an entry in
DIRECT_TEST_CANDIDATES(lib/commands/test.js) so the new file resolves to real tests instead of forcing the full suite. See thetest-laneskill. -
Documentation — the command help text and, if it is a stage or utility, its row in
AGENTS.md.
Rules
- Regenerate, never hand-write, the manifest. Dev-mode discovery masks a
stale manifest locally;
bun build --compileand the drift gate do not. - Exempt means complete, not deferred. A command leaves
coverage.jsonasexemptonly when it is genuinely mapped, routable, and documented — and only in the PR that owns it. A hollow mapping just draws review rounds. - Use Forge's own generator. Re-implementing what the skill CLI already does is a recurring correction here: "why should we do the work". One canonical source, everything else generated. [Forge #5 ×4]
- Names stay short.
status,ready,ship,trace. Long or technical command names are a taste failure in this CLI.
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.
- 2d ago First seen · 63 lines · 54 tokens per session scan A bdaeae868a98
command-surface is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 661 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…