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/gtrabanco/agentic-workflow/ship-roadmapnpx skills add gtrabanco/agentic-workflow --skill ship-roadmapgit clone --depth 1 https://github.com/gtrabanco/agentic-workflowWrote 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/gtrabanco/agentic-workflow/ship-roadmap)<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/ship-roadmap"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/ship-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 | $0.00059 | $0.01735 |
| Opus 5 | $0.00030 | $0.00868 |
| Sonnet 5 | $0.00012 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
ship-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 today.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship the roadmap (autopilot)
Found once, then run the driver-fired loop (Claude /loop, external driver, or
manual re-invocation): plan, implement, review, open and optionally merge one PR
per roadmap unit. After the roadmap, sweep existing issues, ship fix-now work,
report residue as proposals (never create backlog automatically), and print the
final report. Use strong tiers for judgment, cheap tiers for typing, and humans
at expensive-to-undo decisions.
ship-roadmap is the conductor of the loop. It emits its native fixed SHIP:
banner and closing → Next: block; the package-owned machine-result profiles
apply to the worker and sensor skills that a driver invokes inside the loop.
Turn contract — verify before ending the turn
✓ Exactly ONE stage advanced (or a terminal banner printed) and ONE line appended to the run log
✓ Nothing was merged outside the active --fullauto wrapper; direct merge
commands remained blocked and no authorization survived the iteration
✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
✓ The closing `→ Next:` block is printed as the ABSOLUTE last output
Any unchecked box means the turn is not done.
When to use
Use for a locked roadmap with supervision at merge/end points. For one feature, one bug, or exploratory work use the manual planning/execution flow instead.
Step 0 — Discover the project (always first)
Read before acting: CLAUDE.md/AGENTS.md Workflow conventions, documentation
map, docs/features/ROADMAP.md, fix index, architecture doc, and .github/
templates. Then establish:
- Substrate: if the guide, map, roadmap and fix index exist, skip founding and confirm their answers; otherwise founding creates missing pieces.
- Skills: verify
plan-feature,execute-phase,review-change, andaudit-prare installed and record their directory for worker prompts. If absent, stop withnpx skills add gtrabanco/agentic-workflow. With--fullauto, also require executable.agentic-workflow/hooks/fullauto-merge.shand its platform guard; otherwise route toinit-workspace, never direct merge. - Run: existing
docs/features/SHIP_DECISIONS.mdor an opendocs/ship-foundingPR means resume with--continue; bare invocation reports status instead of founding again. - Shape: greenfield/existing, branch, and dirty tree; unexplained dirty default branch stops (never clean it silently).
What ships with it
10 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/ADVANCE.md 8.5 KB
- references/AUDIT_AND_MERGE.md 3.5 KB
- references/CLOSEOUT_AND_LOG.md 1.7 KB
- references/FOUNDING.md 7.6 KB
- references/GUARDRAILS.md 3.8 KB
- references/MODEL_ROUTING.md 2.0 KB
- references/PORTABILITY.md 2.3 KB
- references/RECOVERY_AND_SELECTION.md 6.3 KB
- references/STOP_CONDITIONS.md 1.6 KB
- references/TERMINAL_REPORT.md 2.0 KB
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.
- today Changed a72799a78d79
- 4d ago First seen · 121 lines · 59 tokens per session scan A 23c50119bf2a
ship-roadmap is a skill published in the GitHub repository gtrabanco/agentic-workflow (20 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,735 once invoked, about $0.0003 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
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-phishing
Phishing campaign execution methodology for authorized red team engagements. Covers end-to-end campaign lifecycle: infrastructure provisioning (GoPhish, SMTP relay configuration, domain acquisition and aging, SPF/DKIM/DMARC alignment), payload delivery vectors (Office macro weaponization, HTA droppers, ISO/IMG…
offensive-active-directory
Active Directory attack methodology for internal network red team engagements. Covers reconnaissance (BloodHound, PowerView, ADExplorer), credential abuse (Kerberoasting, ASREProasting, NTLM relay, LLMNR/NBT-NS poisoning), privilege escalation (ACL abuse, GPO abuse, unconstrained/constrained delegation), lateral…