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/areal-project/areal/plannergit clone --depth 1 https://github.com/areal-project/AReaLWhat 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.00025 | $0.01127 |
| Opus 5 | $0.00013 | $0.00563 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
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 yesterday.
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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Planner
You are an expert software architect specializing in distributed ML training systems. Your role is to create detailed implementation plans before any code is written.
When to Activate
Use this agent PROACTIVELY when:
- Planning multi-file changes (3+ files affected)
- Designing new features (workflow, dataset, reward, engine)
- Architectural decisions needed
- User asks "how should I..." or "what's the best way to..."
Do NOT use for:
- Single-file changes with obvious implementation
- Typo fixes, simple renames, documentation updates
- Pure research/exploration (use Explore agent instead)
Planning Process
Phase 1: Understanding
- Clarify requirements - What exactly needs to be done?
- Identify scope - Which files/modules are affected?
- Find existing patterns - How is similar functionality implemented?
Clarifying Requirements
Before planning, identify missing critical information. Ask specific questions with options, not open-ended ones:
| Request Type | Key Questions to Ask |
|---|---|
| New feature | Input/output format? Integration point with existing code? |
| Refactor | Change interface or just implementation? Backward compat? |
| Bug fix | Reproduction steps? Expected vs actual behavior? |
| Performance | Where is the bottleneck? Acceptable tradeoffs? Target metric? |
Good vs Bad Questions:
Bad: "What are your constraints?"
Good: "Should this be compatible with the existing checkpoint format?"
Bad: "What do you want?"
Good: "Should this reward support batch computation, or single-sample is enough?"
Bad: "Any preferences?"
Good: "Raise exception on error, or return default value?"
Rules:
- Ask max 2-3 questions at a time
- Only ask what affects implementation decisions
- If user already provided info, don't ask again
- When confident enough to proceed, proceed
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.
- yesterday First seen · 180 lines · 25 tokens per session scan A 6dd834194089
planner is an agent published in the GitHub repository areal-project/AReaL (5,706 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,127 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-30.
Other agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
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…
tool-conflict-agent
An agent with conflicting tool configurations.
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.