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/sidcorp-co/forge/forge-plannpx skills add SidCorp-co/forge --skill forge-plangit clone --depth 1 https://github.com/SidCorp-co/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.00095 | $0.03667 |
| Opus 5 | $0.00048 | $0.01834 |
| Sonnet 5 | $0.00019 | $0.00733 |
| Haiku 4.5 | $0.00010 | $0.00367 |
Grade A, and why
forge-plan 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Plan
This is the planning step in the issue pipeline: clarified → approved (it runs after triage and clarify). Its job is to turn a triaged, reproduced issue into a concrete implementation plan that a coding agent (or developer) can follow without re-exploring the codebase.
Planning is the highest-value step in the pipeline. A good plan saves the coding step from wasting tokens on exploration, wrong turns, and rework. A bad plan (or no plan) means the coding agent explores blindly, makes architectural mistakes, and produces code that needs heavy review.
Usage
/forge-plan <documentId>
Tools
forge_issues, forge_comments, plus codebase exploration tools (Read, Glob, Grep).
Two-Tier Planning
Not every issue needs deep codebase exploration. The planning depth should match the complexity:
Lightweight plan (xs/s/m): Use project knowledge (forge_knowledge) + issue description + targeted Glob to identify files and write the plan. Read at most 1-2 source files — only when you need to check an existing pattern or verify a component's current props/API. The coding agent will read the files during implementation anyway, so duplicate deep-reading wastes tokens.
Deep plan (l/xl): Full codebase exploration. Read all affected files, trace dependencies, verify patterns. l/xl issues involve architectural decisions where a wrong plan costs more than the exploration.
The tier is determined by the triage comment's complexity classification.
Workflow
Pull-model note: On large issues
forge_step_startreturns a lean manifest (bodyTruncated:true). Fetchplan/description/acceptanceCriteriaas needed viaforge_issues.get { documentId, fields: ['description', 'acceptanceCriteria'] }rather than assuming full body is present.
Step 1: Fetch Issue & Triage Context
Fetch the issue and its comments in parallel:
forge_issues → get → { documentId: "<id>" }
forge_comments → list → { filters: { issue: "<documentId>" } }
forge_config → get
What ships with it
4 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.
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 · 213 lines · 95 tokens per session scan A 5d6454bb3d1d
forge-plan is a skill published in the GitHub repository SidCorp-co/forge (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 95 tokens to every session and 3,667 once invoked, about $0.0005 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
ad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative…
ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad…
adaptive-anti-bot-web-scraping
Adaptive web scraping framework with anti-bot bypass and spider crawling.
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test…
access-gevety-health-biomarker-data
Access your Gevety health data - biomarkers, healthspan scores, biological age, supplements, activities, daily actions, 90-day health protocol, and upcoming tests.
access-exchange-2010-ews-functions
Exchange 2010 EWS integration for emails, calendar, contacts, and tasks.