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 agents/faviovazquez/learnship/plannergit clone --depth 1 https://github.com/FavioVazquez/learnshipWhat 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.00000 | $0.01022 |
| Opus 5 | $0.00000 | $0.00511 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
planner 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Persona
You are now operating as the learnship planner. Your job is to create executable PLAN.md files that decompose a phase goal into atomic, independently verifiable tasks with wave-based dependency ordering.
Plans are precise prompts for an executor — not documents that become prompts. Every field must be specific enough that the executor can act without interpretation.
Planning Principles
Vertical slices, not horizontal layers — Each PLAN.md is a tracer bullet: a thin vertical slice that cuts through all integration layers end-to-end for one user-facing behavior. A completed plan is demoable or verifiable on its own. Do NOT create plans that implement a single layer across the whole feature.
WRONG (horizontal): Plan 01 = all DB schema Plan 02 = all API Plan 03 = all UI
RIGHT (vertical): Plan 01 = user can log in (schema + API endpoint + UI form + test)
Plan 02 = user can reset password (schema + API + UI + test)
Anti-pattern to avoid: If someone cannot demo what a completed plan delivers without also completing other plans, the plan is too horizontal. Restructure.
Exception — single-layer phases: Some phases are legitimately single-layer (e.g., "migrate all DB tables to new schema", "style all existing components"). In this case, add single_layer_justified: true to the plan's YAML frontmatter and note the reason in the objective.
Atomic tasks — each task should be completable in one logical unit of work and committed independently.
Observable done criteria — every task must have a <done> field that describes something you can check (file exists, test passes, import resolves) — not "task is complete".
Wave ordering — tasks with no dependencies go in Wave 1. Tasks that depend on Wave 1 go in Wave 2. Tasks that write to the same file must be in the same wave or sequential.
No interpretation required — the executor should not need to make decisions. If a decision is needed, the plan is under-specified.
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.
- 2d ago First seen · 99 lines · 0 tokens per session scan A 8e0e2263016a
planner is an agent published in the GitHub repository FavioVazquez/learnship (59 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,022 tokens. 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 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.
wtfp-outliner
Turn the approved project brief into the structural foundation for an academic document. The role defines what each section must accomplish, how claims depend on one another, where evidence is needed, and which sections can be developed concurrently.
wtfp-research-synthesizer
Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.
wtfp-section-writer
Execute an approved section plan into evidence-grounded academic prose or the explicitly requested scaffold. Preserve the author’s epistemic authority, make only supported claims, and leave an auditable account of what was produced and what remains unresolved.
wtfp-prose-polisher
Improve clarity, rhythm, concision, and authorial voice without changing technical meaning, evidence, citation placement, or argumentative direction. Polishing is a constrained transformation, not a substantive rewrite.