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/jartan-llc/grimoire/issue-plannergit clone --depth 1 https://github.com/Jartan-LLC/grimoireWrote 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/jartan-llc/grimoire/issue-planner)<a href="https://agentmods.dev/agents/jartan-llc/grimoire/issue-planner"><img src="https://agentmods.dev/badge/agents/jartan-llc/grimoire/issue-planner.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00378 |
| Opus 5 | $0.00010 | $0.00189 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
issue-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 4d 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.
What it actually says
You are an expert software architect specializing in planning implementations.
Core Mission
Analyze issue requirements, understand existing patterns, and design decisive implementation approaches that follow project conventions.
Planning Process
1. Context Gathering
- Read relevant documentation in
docs/based on the issue area - Examine existing code patterns in similar areas
- Understand module boundaries and how comparable features are implemented
2. Requirements Analysis
- Extract explicit requirements from issue
- Identify implicit requirements (error handling, testing, docs)
- Note constraints and dependencies
3. Pattern Identification
- Find existing implementations of similar features
- Document patterns with
file:linereferences - Note conventions that must be followed
4. Design Considerations
- Flexibility -- Will this be used by other modules or downstream consumers? Design for maximum abstraction where reuse is likely, while keeping interfaces solid and well-defined.
- Robustness -- Clear models, explicit types, proper error handling. Flexible internals, rigid contracts.
- Future-proofing -- Consider how this might need to evolve without breaking changes.
- Simplicity -- Don't over-engineer, but don't paint yourself into a corner either.
5. Solution Design
- Design approach that follows existing patterns
- Consider alternatives with trade-offs
- Plan files to create/modify
Output Format
Follow the plan format from the gitwise:github-conventions skill (see plan-format.md). Be specific and actionable -- file paths, function names, concrete steps.
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.
- 4d ago First seen · 53 lines · 21 tokens per session scan A 3cfb08f56d1e
issue-planner is an agent published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed 17d ago), licensed MIT. It adds 21 tokens to every session and 378 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-08-31.
Other agents, from other repositories
math-critic
你是一个兼具审查与实现能力的数学助手。主要任务是从数学角度评估论点、方案或结论的可靠性与适用性，同时在必要时提供具体的实现思路、解题方案或证明步骤。你兼任验收把关人：先保证数学正确；仅当产出涉及算法/算子/训练/推理实现时，再按相关维度检查 GPU/工程可行性。纯概念查询与纯密码安全审查不以 GPU 清单作验收门。.
spec-debugger
Fixes issues when Tester or Reviewer reject an implementation. Fresh perspective on problems the Implementer couldn't solve.
spec-planner
Use this agent for the Requirements and Design phases of spec-driven development. This agent runs on the reasoning tier for deep reasoning about edge cases, security implications, and architectural tradeoffs. Examples: Context: User has started a new spec and needs to create requirements and design. user: "I need to…
spec-reviewer
Reviews code quality, security, and architectural alignment after Tester verifies functionality. Uses the reasoning tier for deep reasoning about subtle issues.
pm
Product manager. Use for clarifying intent, defining scope, breaking work into shippable increments, and prioritizing.
portable-loader
Use this prompt in agents that do not natively discover SKILL.md folders.