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/radimsem/forge-skills/forgenpx skills add radimsem/forge-skills --skill forgegit clone --depth 1 https://github.com/radimsem/forge-skillsWrote 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.
[](https://agentmods.dev/skills/radimsem/forge-skills/forge)<a href="https://agentmods.dev/skills/radimsem/forge-skills/forge"><img src="https://agentmods.dev/badge/skills/radimsem/forge-skills/forge.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00061 | $0.07489 |
| Opus 5 | $0.00030 | $0.03744 |
| Sonnet 5 | $0.00012 | $0.01498 |
| Haiku 4.5 | $0.00006 | $0.00749 |
Grade A, and why
forge scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| any, no CLI / auth error | host REST API per the loaded tracker ref (else generic curl) | How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge
Forge an issue into a shipped fix: heat it (implement), hammer it (review loop), then temper it (refactor).
Overview
Turn an issue or ticket reference into a verified, branch-correct, user-approved plan. Then, only after the user confirms (or immediately under automode), run the implementation lifecycle.
One numbered workflow (Steps 1–12), split by a single gate:
Part 1 — Gate (Steps 1–6): classify → fetch → branch → context → propose → [GATE] approve
Part 2 — Lifecycle (7–12): implement → review-loop → refactor → spin-off → self-evolve → close
gate held: nothing touches the codebase until "yes, implement" (automode = only sanctioned bypass)
- Part 1 — The gate. The contract; do not weaken it.
- Part 2 — Lifecycle. Runs autonomously after approval, stopping only at substantive gates (the Autonomy section).
"The agent" means whatever agent runs this skill. Adapt every reference (config directory, agent guide, interview UI) to your runtime. Nothing is hardcoded to one assistant.
Parameters
Parse the invocation as /forge <ref> [automode] [docs] [tdd] [worktree] [lookup] [secure] [changelog] [ci-watch] [compress] [implement] [codex | codex challenge | codex impl [challenge]] [coderabbit] [code-review], or /forge pr <N> [...], or /forge plan <path>[#<slug>] [...]. The words can appear anywhere in the request. A <ref> resolves to a git-host issue or a Jira ticket per the grammar below, and the pr <N> form selects PR-review entry mode. Flags are orthogonal and compose freely; some modes have their own allowed or ignored flags, listed in references/modes/pr-entry.md for PR mode.
Full flag matrix (effects, composition rules, conflicts): references/flags.md.
Target grammar — <ref>
The target is the first reference-shaped token, or the token right after a ticket or pr keyword. Routing works by keyword or by key-shape:
| Form | Routes to | Examples |
|---|---|---|
bare number, #N, issue N |
git-host issue (Step 1b) | forge 42, fix #123, issue 7 |
matches [A-Z]+-\d+ |
Jira ticket OR Linear issue (disambiguate if both configured — see references/trackers/linear.md) | forge PROJ-123, solve ENG-42, forge AB12-9 |
after ticket keyword |
Jira ticket; number-only → ask project key | forge ticket PROJ-123, solve ticket 42 |
after linear keyword |
Linear issue (forces Linear routing, skips disambiguation) | forge linear ENG-42 |
after pr keyword |
PR-review entry mode (skips Steps 4–7; enters at Step 8 against the PR diff) | forge pr 47, forge pr #123 |
after plan keyword |
plan-entry mode (replaces Steps 1, 2, 4–6 with a single Step P validation pass; Step 3 still runs; enters at Step 7 against the plan slice) | forge plan docs/superpowers/plans/x.md#task-3 |
What ships with it
26 files 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.
- references/anti-patterns.md 1.4 KB
- references/autonomy.md 6.7 KB
- references/flags.md 5.0 KB
- references/mistakes.md 6.7 KB
- references/modes/changelog.md 3.0 KB
- references/modes/ci-watch.md 3.2 KB
- references/modes/codex-impl.md 6.4 KB
- references/modes/compress.md 4.6 KB
- references/modes/implement.md 3.3 KB
- references/modes/lookup.md 3.2 KB
- references/modes/plan-entry.md 6.7 KB
- references/modes/pr-entry.md 5.4 KB
- references/modes/secure.md 2.9 KB
- references/modes/tdd.md 2.0 KB
- references/modes/worktree.md 2.5 KB
- references/proposal-template.md 3.3 KB
- references/red-flags.md 1.9 KB
- references/review-loop.md 4.0 KB
- references/reviewers/code-review.md 2.4 KB
- references/reviewers/coderabbit.md 4.3 KB
- references/reviewers/codex.md 3.8 KB
- references/trackers/github.md 993 B
- references/trackers/gitlab.md 824 B
- references/trackers/jira.md 2.8 KB
- references/trackers/linear.md 4.0 KB
- scripts/resolve-codex.py 2.2 KB runs code
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.
- 4d ago First seen · 329 lines · 61 tokens per session scan A eff84f7e80c5
forge is a skill published in the GitHub repository radimsem/forge-skills (15 stars, last pushed 11d ago), licensed MIT. It adds 61 tokens to every session and 7,489 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…
sales-ops
Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…
jira
Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.
github
Use this skill when Enoch needs to coordinate work with GitHub: branches, pull requests, issues, reviews, comments, checks, and merges.