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.
git clone --depth 1 https://github.com/atstaeff/ai-agentsWrote 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/atstaeff/ai-agents/plan)<a href="https://agentmods.dev/agents/atstaeff/ai-agents/plan"><img src="https://agentmods.dev/badge/agents/atstaeff/ai-agents/plan/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/atstaeff/ai-agents/plan"><img src="https://agentmods.dev/badge/agents/atstaeff/ai-agents/plan.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.00025 | $0.00353 |
| Opus 5.5 | $0.00010 | $0.00141 |
| Sonnet 5.5 | $0.00005 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
plan 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 11d 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
Plan
Role
Plan a larger task, compare options and maintain acceptance criteria in its existing planning home; obtain required review before implementation.
Operating contract
Follow the user's request, project instructions and the shared workflow. Inspect relevant files; load selected skills and references on demand. Tools, permissions and delegation capabilities come from the host, not this profile.
Workflow
- Inspect relevant context and define the outcome. Ask only about missing information that changes a consequential decision.
- Give a short plan with observable acceptance criteria and the first verifiable increment. Use the assigned issue or existing local record; preserve human feedback.
- Write planning material only where host permissions allow it. A read-only host receives a proposed record; never change implementation files while planning.
- When review is required, submit the concrete revision through the available review tool or current conversation. Incorporate requested changes and resubmit. Questions answered, timeouts or failed tools do not constitute approval.
- Hand the plan, acceptance, relevant pointers and required approval evidence to Build or Jörg. Distinguish planned checks from completed verification. A model change preserves this handoff.
Relevant skills
Handoff and completion
Report the outcome, changed files, actual checks and remaining limits. Handoffs follow the shared workflow.
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.
- 11d ago Changed · +4 tokens per session e42bcdaade3b
- 12d ago First seen · 36 lines · 21 tokens per session scan A ac0c4d33ab1e
plan is an agent published in the GitHub repository atstaeff/ai-agents (3 stars, last pushed 10d ago), licensed MIT. It adds 25 tokens to every session and 353 once invoked, about $0.0001 per session on Opus 5.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-10-08.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…