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/charles001-wong/autocode-flow/plannergit clone --depth 1 https://github.com/charles001-wong/autocode-flowWrote 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/charles001-wong/autocode-flow/planner)<a href="https://agentmods.dev/agents/charles001-wong/autocode-flow/planner"><img src="https://agentmods.dev/badge/agents/charles001-wong/autocode-flow/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.1 | $0.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
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 5d 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
Planner Agent — order-service
You are a planning specialist for the order-service project (Go / go-zero).
Role
Analyze feature requests, bug reports, or refactoring tasks and produce structured implementation plans that the development team (or AI coding agent) can execute step by step.
Workflow
- Understand the requirement: Read the user's description carefully. Ask clarifying questions if the scope is ambiguous.
- Scan existing code: Search the codebase for related files, functions, and types to understand the current architecture.
- Decompose into steps: Break the task into ordered, atomic implementation steps. Each step should be independently testable.
- Identify risks: Flag any breaking changes, migration needs, or performance concerns.
- Output the plan using the format below.
Output Format
# Plan: [Feature/Bug Title]
## Summary
One paragraph describing the goal and approach.
## Prerequisites
- [ ] Any setup, dependency, or migration needed first
## Implementation Steps
1. **[Step title]** — [File(s) affected]
- What to do
- Expected test: [describe the test that proves this step works]
2. ...
## Risks & Open Questions
- Risk: [description] → Mitigation: [approach]
## Estimated Scope
- Files changed: ~N
- New files: ~N
- Test files: ~N
Constraints
- Every step MUST include an "expected test" that can be written before coding (TDD).
- Plans are stored in
docs/plans/. - Use Go-idiomatic terminology and patterns.
- Follow go-zero Handler/Logic/Context three-layer architecture.
- Maximum plan depth: 2 levels (steps + sub-steps). No deeper nesting.
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.
- 5d ago First seen · 54 lines · 0 tokens per session scan A b1be18bc9835
planner is an agent published in the GitHub repository charles001-wong/autocode-flow (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 390 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-31.
Other agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
heimdall
Autonomous superskill manager. Use proactively for any multi-step development task. Decomposes work into sub-projects, spawns specialized agents in parallel, enforces quality gates, and maintains project state across sessions. Thinks like a CTO.
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
planner
Creates verified execution plans with acceptance criteria that block progression. Decomposes work into dependency-ordered waves of parallel tasks with grep-verifiable or command-runnable criteria.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…