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/firatcand/forge/amend-roadmapnpx skills add firatcand/forge --skill amend-roadmapgit clone --depth 1 https://github.com/firatcand/forgeWrote 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/firatcand/forge/amend-roadmap)<a href="https://agentmods.dev/skills/firatcand/forge/amend-roadmap"><img src="https://agentmods.dev/badge/skills/firatcand/forge/amend-roadmap.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.1 | $0.00047 | $0.01439 |
| Opus 5 | $0.00023 | $0.00720 |
| Sonnet 5 | $0.00009 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
amend-roadmap 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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/amend-roadmap
Mid-flight roadmap mutation. The user has a new task ("we need a caching layer task, depends on T05") and wants it in the roadmap WITHOUT hand-editing phases.yaml or the tracker.
Skill ↔ verb split: this skill collects the fields, previews the plan, and confirms. ALL state mutation goes through forge orchestrate amend-roadmap, which is tracker-first: it creates the tracker issue, wires blocked-by relations, then materializes the task into plans/phases.yaml through the reconcile --pull machinery (staged addition) — phases.yaml stays single-writer. Every step is journaled and resumable.
Preconditions
plans/phases.yamlexists, validates, and has asource:stanza (tracker-bound). If there is nosource:stanza, stop: run/push-to-tracker(greenfield) or/reconcile --pullfirst..forge/settings.yamlhas a workingtracker:block.
Step 1 — Collect fields
Prompt the user for (one round, AskUserQuestion where it helps):
| Field | Constraint |
|---|---|
phase |
existing phase-N[.M] id — show the active phases to pick from |
title |
verb + noun, ≤ 8 words |
description |
1 paragraph |
type |
foundation · data · backend · integration · content · infra · skill · docs |
priority |
P0 · P1 · P2 |
estimate |
S · M · L — XL is refused by the verb ("No XL tasks ship — split them") |
owner_type |
backend-dev · frontend-dev · db-architect · devops-engineer · qa-engineer · security-auditor · design-engineer · integration · human (manual bootstrap work — never auto-dispatched) |
acceptance |
≥ 1 concrete, testable criteria |
depends_on |
task ids (P2-T03) or tracker identifiers (FORGE-93); every dep must already exist AND be tracker-backed |
write_globs |
optional — file globs for overlap classification |
Step 2 — Preview + confirm
Show the user the assembled payload plus what will happen:
New task in phase-2.5 (next id will be computed by the verb, e.g. P2.5-T14):
title: Add caching layer for tracker reads
type/prio: backend · P1 · M · backend-dev
depends_on: P2.5-T03 (FORGE-95)
Plan: 1 tracker issue + 1 blocked-by relation → phases.yaml via reconcile pull.
Proceed? [y/n]
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.
- 5d ago First seen · 123 lines · 47 tokens per session scan A 07b0372d1a74
amend-roadmap is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,439 once invoked, about $0.0002 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.
Other skills, from other repositories
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
prospec-knowledge-generate
Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.
submit-pr
Open a prospec pull request in the house format — push the change's two commits, write the Traditional Chinese body, and link it to its issue. Triggers: submit pr, open pr, 開 PR, 送 PR, 發 PR, pull request, 提交 PR.
submit-issue
Open a prospec GitHub issue in the house format — conventional-commit title, Traditional Chinese body (problem → solutions → acceptance criteria), downstream-compatibility block, series cross-links, and optional model-routing guidance. Triggers: submit issue, open issue, create issue, file issue, 開 issue, 發 issue, 建…
prospec-explore
Explore - Requirement exploration, problem investigation, and solution comparison partner. Triggers: explore, compare, investigate, unsure, clarify, 探索, 比較, 釐清, 調查, 不確定.
prospec-plan
Plan Implementation - Convert User Story into technical implementation plan (plan.md) and change specification (delta-spec.md). Triggers: plan, architecture, technical plan, 規劃, 架構規劃, 技術規劃.