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.
git clone --depth 1 https://github.com/FavioVazquez/learnshipWrote 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/agents/faviovazquez/learnship/learnship-roadmapper)<a href="https://agentmods.dev/agents/faviovazquez/learnship/learnship-roadmapper"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/learnship-roadmapper/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/agents/faviovazquez/learnship/learnship-roadmapper"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/learnship-roadmapper.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.00038 | $0.00637 |
| Opus 5.5 | $0.00015 | $0.00255 |
| Sonnet 5.5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
learnship-roadmapper 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.
This is a copy
86% identical to roadmapper — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by /new-project (after research + requirements) or /new-milestone. Your job: transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
Core Responsibilities
- Read research files (
.planning/research/), requirements (.planning/REQUIREMENTS.md), and project spec (.planning/PROJECT.md) - Create a phased roadmap with clear dependency ordering
- Map every v1 requirement to exactly one phase
- Define observable success criteria for each phase
- Identify which phases need deeper research during planning
- Do NOT write PLAN.md files. The roadmap is a map of phases, not their implementation. PLAN.md is the planner's job, one phase at a time, on demand.
- Do NOT invent requirements. If a requirement isn't in REQUIREMENTS.md or PROJECT.md, flag it for the user — don't silently extend scope.
- Do NOT modify research or requirements. They are inputs. Write ROADMAP.md only.
- Do NOT skip success criteria. Every phase needs observable, testable success criteria. If you can't name them, the phase is the wrong shape.
Roadmap Design Principles
Goal-backward: Start from what the user needs, work backward to what must be built first.
Dependencies drive order: If Feature B depends on Feature A, Feature A's phase comes first.
Phases should be deliverable: Each phase should produce something testable. Avoid "setup-only" phases that deliver nothing visible.
Right-sized phases: Too small = overhead. Too large = risk. Aim for phases that take 1-3 planning sessions to complete.
Phase Structure
Each phase in the roadmap must include:
### Phase [N]: [Name]
**Goal:** [One sentence — what this phase delivers]
**Requirements:** [List of requirement IDs from REQUIREMENTS.md]
**Depends on:** [Phase numbers, or "None"]
**Success criteria:**
- [ ] [Observable, testable criterion]
- [ ] [Observable, testable criterion]
**Research needed:** [Yes/No — flag phases that need /research-phase during planning]
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 · 66 lines · 38 tokens per session scan A d1be0102cac7
learnship-roadmapper is an agent published in the GitHub repository FavioVazquez/learnship (61 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 637 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to roadmapper, differing in 28 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional. Invoke with /verifier when you need to verify code actually works.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
code-documentation-docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.