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 skills add firatcand/forge --skill delivergit 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/deliver)<a href="https://agentmods.dev/skills/firatcand/forge/deliver"><img src="https://agentmods.dev/badge/skills/firatcand/forge/deliver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/firatcand/forge/deliver"><img src="https://agentmods.dev/badge/skills/firatcand/forge/deliver.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.04599 |
| Opus 5.5 | $0.00026 | $0.01840 |
| Sonnet 5.5 | $0.00013 | $0.00920 |
| Haiku 4.5 | $0.00006 | $0.00460 |
Grade A, and why
deliver 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 1mo 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deliver
/deliver <phase-id | --all> drives a whole band of work — a phase, a
feature-set, or the entire roadmap — toward "merged + Done", by grouping ready
tickets into themed batches and driving each batch through the per-ticket
/drive gauntlet. It is the long-horizon recipe above /drive: /drive
delivers one ticket; /deliver sequences and batches many, front-loads the
architectural decisions, and runs the phase-gate ceremony at phase boundaries.
This is the vision headline — use loops, goals, and the gauntlet to deliver a
full phase/feature-set/product by asking the user mainly architectural
questions — codified into a reusable skill that orchestrates the EXISTING
skills (/drive, /pickup-task, /plan-task, /implement, /review,
/second-opinion, /ship, /wrap-up, /phase-gate) and read verbs.
This is a per-turn recipe — NOT a loop (ADR)
/deliver does all it can in one invocation and then RETURNS. It MUST NOT
self-loop: no sleep, no watch, no while true, no --follow, no
gh pr checks --watch. Whenever the next step is an asynchronous wait — CI
running, a human decision pending — /deliver reports the state and returns.
The repeat-until-done behavior is owned by the native /goal driver:
/goal "phase-4 delivered" # or: /goal "v0.5 delivered"
and the host re-invokes /deliver <band> each turn until every ticket in the
band is merged and Done. Keeping the loop in native /goal//loop (not here) is
what lets every round run as a fresh, fully-budgeted interactive turn — the
autopilot ADR decision (spec/decisions / the native-/goal ADR). /deliver is
the recipe; /goal is the engine. Within one turn /deliver may drive several
batches sequentially, but it never wraps itself in its own loop.
Runs on the interactive skill path (NOT the formal dispatch lifecycle)
/deliver uses the SAME interactive recipe as /drive and /pickup-task:
tracker status (set natively) + ensure-worktree + /plan-task +
/implement + /review + /second-opinion + /ship + tracker-Done +
/wrap-up (whose gc --remove-worktrees removes the worktree). It does NOT
drive the formal claim → dispatch → heartbeat → complete state machine — that
is the HEADLESS-orchestrator path. This matters two ways:
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.
- 1mo ago First seen · 335 lines · 64 tokens per session scan A 586a84dddc3b
deliver is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 4,599 once invoked, about $0.0003 per session on Opus 5.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
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-quick-batch
Batch several /gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-workspace
Manage GSD workspaces — create, list, or remove isolated workspace environments.
gsd-inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.