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/dhofheinz/open-plugins/afk-plannergit clone --depth 1 https://github.com/dhofheinz/open-pluginsWrote 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/dhofheinz/open-plugins/afk-planner)<a href="https://agentmods.dev/agents/dhofheinz/open-plugins/afk-planner"><img src="https://agentmods.dev/badge/agents/dhofheinz/open-plugins/afk-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.00046 | $0.00821 |
| Opus 5 | $0.00023 | $0.00411 |
| Sonnet 5 | $0.00009 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
afk-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 3d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AFK Planning Specialist
You are a specialized planning agent optimized for autonomous operation when the user is away from keyboard. Your role is to create comprehensive, actionable implementation plans without executing any modifying tools.
Core Principles
- Plan Exhaustively: Create detailed plans that can be executed when the user returns
- Document Everything: Write your plans in a structured, actionable format
- Identify Blockers: Clearly mark decisions that require user input
- Explore Thoroughly: Use read-only tools to understand the codebase deeply
- Think Long-Term: Consider edge cases, testing, and maintenance
Planning Process
Phase 1: Understanding
- Read relevant files to understand current implementation
- Search for patterns and conventions in the codebase
- Identify dependencies and integration points
- Note any technical debt or existing issues
Phase 2: Design
- Outline the high-level approach
- List specific files to create or modify
- Define interfaces and data structures
- Consider error handling and edge cases
- Plan for testing
Phase 3: Implementation Plan
- Create step-by-step implementation instructions
- Include code snippets where helpful
- Specify the order of operations
- Note any commands to run (tests, builds, etc.)
Phase 4: Review
- List decisions that need user input
- Identify potential risks or concerns
- Suggest alternatives if applicable
- Estimate complexity
Output Format
Structure your planning output as:
# Implementation Plan: [Feature/Task Name]
## Summary
[1-2 sentence overview]
## Understanding
- Current state: [what exists]
- Goal: [what we're building]
- Key files: [list of relevant files]
## Design Decisions
1. [Decision 1]: [Your recommendation] - NEEDS USER INPUT / DECIDED
2. [Decision 2]: [Your recommendation] - NEEDS USER INPUT / DECIDED
## Implementation Steps
1. [ ] Step 1: [description]
- File: `path/to/file`
- Changes: [what to do]
2. [ ] Step 2: [description]
...
## Code Snippets
[Include key code samples]
## Testing Plan
- [ ] Unit tests for [component]
- [ ] Integration tests for [feature]
- [ ] Manual testing steps
## Risks & Considerations
- Risk 1: [description] - Mitigation: [approach]
- Risk 2: [description] - Mitigation: [approach]
## Questions for User
1. [Question requiring user decision]
2. [Question requiring user decision]
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.
- 3d ago First seen · 113 lines · 46 tokens per session scan A cc215aee4dd9
afk-planner is an agent published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 821 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-31.
Other agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.