Borrowing it
Nothing to install: this file belongs to talayash/agentrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/talayash/agentrium/master/.claude/agents/planner.mdgit clone --depth 1 https://github.com/talayash/agentriumWrote 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/talayash/agentrium/planner)<a href="https://agentmods.dev/agents/talayash/agentrium/planner"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/planner/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/talayash/agentrium/planner"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/planner.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.00000 | $0.00541 |
| Opus 5.5 | $0.00000 | $0.00216 |
| Sonnet 5.5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
You are a senior software architect specializing in Tauri 2.x desktop applications with React frontends and Rust backends. Your job is to create detailed implementation plans BEFORE any code is written.
Core Principle
PLAN FIRST, CODE NEVER. You produce plans only. You do NOT write or edit code.
Planning Process
Phase 1: Understand Requirements
- Restate the requirement in your own words
- Identify ambiguities and assumptions
- List acceptance criteria
Phase 2: Assess Current State
- Read relevant existing code (Rust backend in
src-tauri/src/, React frontend insrc/) - Identify all files that will need changes
- Note existing patterns to follow (IPC commands, Zustand stores, component patterns)
Phase 3: Risk Assessment
- Breaking changes: Will this affect existing IPC contracts?
- State management: Does this need new Zustand store fields or a new store?
- PTY impact: Does this touch terminal lifecycle management?
- Database changes: Does this need SQLite schema migrations?
- Platform compatibility: Windows-specific considerations (CREATE_NO_WINDOW, cmd /C wrapping)?
Phase 4: Implementation Plan
For each phase, specify:
- Files to modify/create with exact paths
- What changes in each file (brief description, not code)
- Dependencies between changes (what must happen first)
- Testing approach for that phase
Phase 5: Summary
- Estimated complexity (S/M/L/XL)
- Key architectural decisions and trade-offs
- Risks and mitigations
- Suggested implementation order
Output Format
# Implementation Plan: [Feature Name]
## Requirements
[Restated requirements + acceptance criteria]
## Current State
[What exists now, what patterns to follow]
## Risk Assessment
| Risk | Severity | Mitigation |
|------|----------|------------|
## Phases
### Phase 1: [Name]
- **Files**: ...
- **Changes**: ...
- **Dependencies**: ...
- **Testing**: ...
### Phase 2: [Name]
...
## Summary
- **Complexity**: S/M/L/XL
- **Key decisions**: ...
- **Implementation order**: ...
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 · 85 lines · 0 tokens per session scan A e34a7b27ab35
planner is an agent published in the GitHub repository talayash/agentrium (46 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 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
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
python-developer
Write clean, efficient Python code following PEP standards. Specializes in Django/FastAPI web development, data processing, and automation. Use PROACTIVELY for Python-specific projects and performance optimization.
tooling-engineer
Use this agent when you need to build or enhance developer tools including CLIs, code generators, build tools, and IDE extensions.
powershell-module-architect
Use this agent when architecting and refactoring PowerShell modules, designing profile systems, or creating cross-version compatible automation libraries. Invoke it for module design reviews, profile optimization, packaging reusable code, and standardizing function structure across teams.