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/sifxprime/kodelyth-eccWrote 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/commands/sifxprime/kodelyth-ecc/prp-plan)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/prp-plan"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/prp-plan/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/commands/sifxprime/kodelyth-ecc/prp-plan"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/prp-plan.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.00012 | $0.03329 |
| Opus 5.5 | $0.00005 | $0.01332 |
| Sonnet 5.5 | $0.00002 | $0.00666 |
| Haiku 4.5 | $0.00001 | $0.00333 |
Grade A, and why
prp-plan 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
98% identical to prp-plan — 10 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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapted from PRPs-agentic-eng by Wirasm. Part of the PRP workflow series.
PRP Plan
Create a detailed, self-contained implementation plan that captures all codebase patterns, conventions, and context needed to implement a feature in a single pass.
Core Philosophy: A great plan contains everything needed to implement without asking further questions. Every pattern, every convention, every gotcha — captured once, referenced throughout.
Golden Rule: If you would need to search the codebase during implementation, capture that knowledge NOW in the plan.
Phase 0 — DETECT
Determine input type from $ARGUMENTS:
| Input Pattern | Detection | Action |
|---|---|---|
Path ending in .prd.md |
File path to PRD | Parse PRD, find next pending phase |
Path to .md with "Implementation Phases" |
PRD-like document | Parse phases, find next pending |
| Path to any other file | Reference file | Read file for context, treat as free-form |
| Free-form text | Feature description | Proceed directly to Phase 1 |
| Empty / blank | No input | Ask user what feature to plan |
PRD Parsing (when input is a PRD)
- Read the PRD file with
cat "$PRD_PATH" - Parse the Implementation Phases section
- Find phases by status:
- Look for
pendingphases - Check dependency chains (a phase may depend on prior phases being
complete) - Select the next eligible pending phase
- Look for
- Extract from the selected phase:
- Phase name and description
- Acceptance criteria
- Dependencies on prior phases
- Any scope notes or constraints
- Use the phase description as the feature to plan
If no pending phases remain, report that all phases are complete.
Phase 1 — PARSE
Extract and clarify the feature requirements.
Feature Understanding
From the input (PRD phase or free-form description), identify:
- What is being built (concrete deliverable)
- Why it matters (user value)
- Who uses it (target user/system)
- Where it fits (which part of the codebase)
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 · 503 lines · 12 tokens per session scan A d7dfc27704da
prp-plan is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 14d ago), licensed MIT. It adds 12 tokens to every session and 3,329 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to prp-plan, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
learn
Analyze the current session and extract any patterns worth saving as skills.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.