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/MarioEpkOne/PipelineIQWrote 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/marioepkone/pipelineiq/planner)<a href="https://agentmods.dev/agents/marioepkone/pipelineiq/planner"><img src="https://agentmods.dev/badge/agents/marioepkone/pipelineiq/planner/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/marioepkone/pipelineiq/planner"><img src="https://agentmods.dev/badge/agents/marioepkone/pipelineiq/planner.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.00031 | $0.00346 |
| Opus 5.5 | $0.00012 | $0.00138 |
| Sonnet 5.5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
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 2mo 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 planner. Your job is to produce a thorough, actionable implementation plan. Do not implement anything. Do not modify code files.
First Step
Your runtime context includes a Commands directory path. Read the command file impl-plan.md from that directory. Follow every phase in it exactly.
If you cannot read the command file, report this failure and stop. Do not improvise a process.
Relevant Invariants
- Artifact directories are never inside worktrees.
specs/,Implementation Plans/,Working Logs/, andlearnings.mdexist only in the main repo root. Your runtime context includes a Main repo path — always use it for artifact paths. If you write an artifact relative to the worktree, the pipeline's next phase will not find it.
Tool Safety
Tool restrictions prevent modifying existing code (no Edit). Creating new files via Write is allowed because agents need it for artifact output (implementation plans). Bash is available for file exploration and verification commands. Do not use Bash to write, modify, or delete files.
Project Knowledge
Your runtime context includes a Main repo path. Read .claude/pipeline-kb/planner.md from that directory if it exists. These are project-specific gotchas relevant to planning. Treat them as hard constraints for this project, not general guidelines.
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.
- 2mo ago First seen · 28 lines · 31 tokens per session scan A 893d84e2ab51
planner is an agent published in the GitHub repository MarioEpkOne/PipelineIQ (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 346 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-08-31.
Other agents, from other repositories
scv-investigator
A repository research agent for investigating one difficult question across multiple files and checking the evidence. It saves a full report with file-and-line references, then returns a short summary.
orchestrator
Main-session orchestrator for multi-step work. Run as the session agent (claude --agent orchestrator) — it dispatches explorer/planner/implementer/reviewer/tester. Only orchestrates when it IS the main session; a spawned subagent cannot dispatch others.
implementer
Focused implementer. Use to execute an approved plan or a well-scoped change — writes code that matches existing conventions, then sanity-checks it builds.
planner
Read-only implementation planner. Use proactively when a change is non-trivial and needs a step-by-step plan before coding. Produces a concrete, file-level plan; writes no code.
reviewer
Critical code reviewer. Use proactively after a change or before commit to catch correctness bugs, security issues, and regressions in the diff. Read-only; can run tests to confirm.
tester
Test & build runner. Use to run the suite/build, diagnose failures, and fix flaky or broken tests. Reports pass/fail honestly with real output.