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/soulcodex/agentic/technical-roadmap-planningnpx skills add soulcodex/agentic --skill technical-roadmap-planninggit clone --depth 1 https://github.com/soulcodex/agenticWhat 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.01001 |
| Opus 5 | $0.00030 | $0.00500 |
| Sonnet 5 | $0.00012 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
technical-roadmap-planning 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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Roadmap Planning Skill
Step 1 — Gather Inputs
Before defining initiatives, collect:
- Business objectives for the period (OKRs, product strategy, growth targets).
- Tech debt inventory — known architectural problems, reliability gaps, security risks.
- Reliability data — incident history, SLA breaches, on-call burden.
- Team capacity — headcount, planned leave, hiring timeline.
- Dependencies — migrations, third-party deprecations, compliance deadlines.
Ask the user to provide or confirm these inputs before proceeding.
Step 2 — Define Initiatives
For each initiative, capture:
Initiative: <name>
Problem: <what is broken or missing — one sentence>
Metric: <how success is measured — must be quantifiable>
Effort: <S | M | L | XL> (S=days, M=weeks, L=1-2 months, XL=quarter+)
Impact: <Low | Medium | High | Critical>
Dependencies: <other initiatives or teams this blocks or is blocked by>
Example:
Initiative: Database connection pooling
Problem: Under peak load, the API exhausts the DB connection limit, causing 503s.
Metric: Zero connection-limit errors in staging load test at 2× current peak traffic.
Effort: S
Impact: High
Dependencies: None
Step 3 — Prioritise (Impact / Effort Matrix)
Plot each initiative on a 2×2 grid and apply the priority rules:
Impact
High │ Quick Wins ★ │ Strategic Bets ◆
│ (do now) │ (plan carefully)
├──────────────┼──────────────────
Low │ Fill-ins │ Avoid / defer
│ (if capacity)│
└──────────────┴────────────────
Low Effort High Effort
| Priority | Quadrant | Action |
|---|---|---|
| 1 | High Impact + Low Effort | Schedule immediately |
| 2 | High Impact + High Effort | Plan with milestones |
| 3 | Low Impact + Low Effort | Fill between larger items |
| 4 | Low Impact + High Effort | Defer or remove |
Mark compliance/security items as non-negotiable regardless of quadrant.
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.
- 3d ago First seen · 125 lines · 59 tokens per session scan A 9e66b6633566
technical-roadmap-planning is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,001 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-31.
Other skills, from other repositories
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).