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 liqiongyu/lenny_skills_plus --skill technical-roadmapsgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/technical-roadmaps)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/technical-roadmaps"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/technical-roadmaps/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/liqiongyu/lenny_skills_plus/technical-roadmaps"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/technical-roadmaps.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.00023 | $0.01991 |
| Opus 5 | $0.00012 | $0.00996 |
| Sonnet 5 | $0.00005 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
technical-roadmaps 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 9d 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 Roadmaps
Scope
Covers
- Turning "technical work" (architecture, platform, reliability, tech debt) into a written strategy + roadmap that stakeholders can critique and improve.
- Applying Richard Rumelt's strategy frame (Diagnosis → Guiding policy → Coherent actions) to engineering planning.
- Producing a roadmap that is executable (owners, milestones, dependencies, risks, metrics), not a vague wishlist.
- Aligning a technical roadmap with product/business constraints (quarters, launches, compliance/security, capacity).
When to use
- "Create a technical/engineering/architecture roadmap for the next 2–4 quarters."
- "We need a written technical strategy and a roadmap we can review with leadership."
- "We have many tech-debt/platform initiatives; turn them into a prioritized plan with dependencies and milestones."
- "Our tech roadmap keeps being misunderstood—write it down so we can debug alignment."
When NOT to use
- The problem/outcome is unclear (use
problem-definitionfirst). - You need to choose which product bets matter most (use
prioritizing-roadmaporai-product-strategy). - You only need delivery dates, milestone tracking, and RAG governance (use
managing-timelines). - You need a deep platform strategy / ecosystem design (use
platform-infrastructure). - You want to improve engineering team processes, hiring, or culture norms (use
engineering-culture). - You need a product roadmap oriented around user-facing features and business outcomes rather than technical infrastructure (use
prioritizing-roadmap).
Inputs
Minimum required
- Audience + decision: who this roadmap is for (Eng leadership, Execs, Product) and what decisions it must enable.
- Time horizon + format: e.g., 6 months / 12 months; Now-Next-Later vs quarterly.
- Current-state diagnosis inputs: top pain points, reliability/latency/cost signals, incident themes, scaling constraints, key architectural bottlenecks.
- Constraints: capacity assumptions, compliance/security requirements, platform constraints, non-negotiables.
- Candidate initiatives: known platform/architecture/tech-debt items (even a rough list).
What ships with it
13 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.
- eval/eval_config.json 625 B
- eval/SHOWCASE.md 5.4 KB
- eval/with_skill.md 42 KB
- eval/without_skill.md 16 KB
- README.md 1.0 KB
- references/CHECKLISTS.md 1.5 KB
- references/EXAMPLES.md 1.4 KB
- references/INTAKE.md 1.8 KB
- references/RUBRIC.md 4.7 KB
- references/SOURCE_SUMMARY.md 812 B
- references/TEMPLATES.md 2.4 KB
- references/WORKFLOW.md 3.7 KB
- skillpack.json 371 B
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.
- 9d ago First seen · 125 lines · 23 tokens per session scan A 42ef16ad13b7
technical-roadmaps is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,991 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
cangjie-skill
A process for turning a book, course, podcast, interview, long video, or other long material into reusable instructions for an AI agent. It extracts methods and principles, checks them, and packages them as skills.
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…
loop-library
Compatibility alias for Loopy. Use only when an existing installation or older instruction explicitly invokes loop-library; use Loopy for new installations and requests. Provides the same discovery, recommendation, audit, repair, adaptation, guided crafting, bounded execution, run debrief, project loop saving, and…
naval-almanack
A reference guide for applying ideas from The Almanack of Naval Ravikant, a book about wealth, work, happiness, judgment, and long-term thinking. It routes questions to the relevant topic guidance and notes when professional help is needed.
decision-heuristics
A set of heuristics for making difficult personal decisions such as changing jobs, buying a home, moving, forming a partnership, or getting married. It is intended for major choices, not everyday decisions.
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.