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/using-forgenpx skills add harshanandak/forge --skill using-forgegit 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.00234 | $0.01383 |
| Opus 5 | $0.00117 | $0.00691 |
| Sonnet 5 | $0.00047 | $0.00277 |
| Haiku 4.5 | $0.00023 | $0.00138 |
Grade A, and why
using-forge 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. You cannot rationalize your way out of it.
The rule
Invoke the relevant or requested Forge skill BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to follow it — but you check first.
Then announce Using [skill] to [purpose] and follow the skill exactly. If it has a
checklist or HARD-GATE, create one todo per item.
When unsure WHICH skill fits, either consult the routing table below or run
forge skill for "<what you are about to do>" for a deterministic best-fit answer.
Intent → skill routing table
Process skills set the approach first; then the stage/implementation skill carries it out.
| When the situation is… | Start with |
|---|---|
| "Add / build / scope a new feature", "let's build X" | plan |
| Implement a task that a plan already defined | dev |
| "Fix this bug" / a failing test / unexpected behavior | dev (if superpowers:systematic-debugging is installed, apply its technique first, then implement via dev) |
| Run type-check, lint, security, or tests | validate |
| Push the branch and open a PR | ship |
| Address PR / review-agent feedback (CodeRabbit, Greptile, CI) | review |
| Post-merge health check, close issues | verify |
| "What should I work on?" — rank the ready queue | triage-ready |
| "Where am I?" / current stage / stale or active work | status |
| Create / update / close / search / comment on ONE issue | issue-basics |
| Claim an issue and PROVE the lease before mutating | claim-safety |
| Drive one issue plan→merged-PR under human gates | smith |
| Monitor / shepherd a PR's CI + checks (never merges) | shepherd |
| Deep, multi-source web research | research / parallel-deep-research |
| "How does Forge fit together?" / which verb for X | kernel |
| Safe revert / undo a merged change | rollback |
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.
- 2d ago First seen · 105 lines · 234 tokens per session scan A 487357f80757
using-forge is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 2d ago), licensed MIT. It adds 234 tokens to every session and 1,383 once invoked, about $0.0012 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.