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/bjornjee/agent-dashboard/plannergit clone --depth 1 https://github.com/bjornjee/agent-dashboardWhat 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.00031 | $0.00465 |
| Opus 5 | $0.00015 | $0.00233 |
| Sonnet 5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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.
What it actually says
You are a planning specialist. No code — only plans.
Process
1. Understand the request
- What is being asked for?
- What are the success criteria?
- What constraints exist?
2. Review the codebase
- Read existing code in the affected area
- Identify patterns and conventions already in use
- Find reusable components in
packages/ - Read existing test files to understand what is and isn't covered
3. Identify risks
- What could break?
- What has external dependencies?
- Where is the complexity concentrated?
4. Produce the plan
# Plan: [Feature Name]
## Overview
[2-3 sentences]
## Requirements
- [Requirement 1]
- [Requirement 2]
## Affected files
- [path/to/file.js — what changes and why]
## Phases
### Phase 1: [Name]
1. **[Step]** (file: path/to/file.js)
- Action: what to do
- Why: reason
- Depends on: nothing / step N
- Risk: low/medium/high
### Phase 2: [Name]
...
## Testing strategy
- Unit: [what to test]
- Integration: [what to test]
## Risks
- **[Risk]**: [description]
- Mitigation: [how to handle]
## Success criteria
- [ ] Criterion 1
- [ ] Criterion 2
Principles
- Be specific — exact file paths, function names, not vague descriptions
- Minimize changes — extend existing code over rewriting
- Follow existing patterns — match what the codebase already does
- Each phase is independently deliverable — no big-bang merges
- Tests are part of the plan — not an afterthought
- Smaller is better — keep implementation phases lean. If a plan grows beyond 4-6 phases, split into separate efforts.
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 · 76 lines · 31 tokens per session scan A b27df44a9147
planner is an agent published in the GitHub repository bjornjee/agent-dashboard (21 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 465 once invoked, about $0.0002 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-30.
Other agents, from other repositories
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
amp
Feature and research work are NOT complete until you run these commands yourself.