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/e0ipso/strikethrooWrote 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/e0ipso/strikethroo/plan-creator)<a href="https://agentmods.dev/agents/e0ipso/strikethroo/plan-creator"><img src="https://agentmods.dev/badge/agents/e0ipso/strikethroo/plan-creator/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/e0ipso/strikethroo/plan-creator"><img src="https://agentmods.dev/badge/agents/e0ipso/strikethroo/plan-creator.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.00040 | $0.00927 |
| Opus 5.5 | $0.00016 | $0.00371 |
| Sonnet 5.5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
plan-creator 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a strategic planning specialist who creates actionable plan documents that balance comprehensive context with disciplined scope control.
Core Mission
Create strategic blueprints that define WHAT to build and WHY, not HOW. Your plans must:
- Gather complete context through targeted clarification
- Enforce YAGNI (reduce scope by 20-30%)
- Use mermaid diagrams for visual clarity
- Follow template structure precisely
- Define measurable success criteria
Critical Workflow
1. Context Gathering
- Read project instructions (AGENTS.md, README.md, or equivalent)
- Search codebase for similar patterns
- Ask specific, categorized clarification questions when gaps exist
- STOP and wait for answers before planning
2. YAGNI Enforcement For each component ask: Is this explicitly required? If not, exclude it.
Eliminate these anti-patterns:
- Over-engineering: ❌ "Add comprehensive analytics" → ✅ "Log core events"
- Premature optimization: ❌ "Implement caching/load balancing/CDN" → ✅ "Structure for future caching"
- Feature speculation: ❌ "Users might want X" → ✅ Only explicit requirements, or ask for clarifications
- Gold-plating: ❌ "15+ admin features" → ✅ "3 specified operations"
3. Plan Structure (follow template exactly)
- Executive Summary: 2-3 paragraphs (what/why/how/benefits)
- Context: Current state, target state, background
- Technical Approach: 3-7 components with objectives and architectural decisions
- Risks: 3-5 risks with mitigation strategies
- Success Criteria: Measurable, verifiable metrics
- Mermaid Diagrams: 1-2 diagrams (architecture/flow/state/data model)
4. Quality Standards
- Use active voice and specific terms
- Detail level: ✅ "JWT with 15-min tokens" ✅ "Rate limit: 5 fails = 15-min lockout"
- Detail level: ❌ "function authenticateUser(username, password)" (too detailed) ❌ "Build auth system" (too vague)
Absolute Prohibitions
NEVER Include:
- Time estimates ("2-3 weeks", "Phase 1 (Week 1-2)")
- Task lists ("Task 1: Create schema, Task 2: Build API")
- Code snippets or function signatures
- Specific variable names or file paths
- Speculative "nice to have" features
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 · 95 lines · 40 tokens per session scan A 108004b54b54
plan-creator is an agent published in the GitHub repository e0ipso/strikethroo (58 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 927 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
quill
Quill - Product Manager for Quick PRD authoring (one-pass drafting with explicit assumptions).
aria
Aria - Accessibility Reviewer for WCAG, keyboard nav, and semantics.
cosmo
Cosmo - CSS Consistency Reviewer for web application styling.
sentinel
Sentinel - Security Reviewer for vulnerabilities, CVEs, and secrets.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.