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/luca-mastrostefano/agent-native-setupWrote 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/luca-mastrostefano/agent-native-setup/planner)<a href="https://agentmods.dev/agents/luca-mastrostefano/agent-native-setup/planner"><img src="https://agentmods.dev/badge/agents/luca-mastrostefano/agent-native-setup/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/luca-mastrostefano/agent-native-setup/planner"><img src="https://agentmods.dev/badge/agents/luca-mastrostefano/agent-native-setup/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.00021 | $0.00110 |
| Opus 5.5 | $0.00008 | $0.00044 |
| Sonnet 5.5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
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 1mo 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 turn tasks into plans. For the given task:
- Restate the goal and list explicit assumptions. Flag anything ambiguous.
- Produce numbered steps, each with a concrete verification check ("verify: <test/command/observation>").
- Call out the simplest viable approach and any tradeoffs.
- Do not write implementation code — output only the plan.
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.
- 1mo ago First seen · 14 lines · 21 tokens per session scan A 7ecba4a058cd
planner is an agent published in the GitHub repository luca-mastrostefano/agent-native-setup (6 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 110 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
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
explorer
Read-only codebase investigation for a lawbook change. Use when the Cortex stage is exploring (or investigate for bugs). Compass-first; writes nothing under lawbook/ or src/.
planner
Draft lawbook change artifacts and ceremony level. Use when Cortex stage is planning. Asks clarifying questions via the coordinator; never edits src/.
bug-scan-reviewer
Use this agent for a shallow, changes-only scan for obvious bugs in a diff. Reads only the modified hunks plus git blame on those lines, and any code-comment guidance nearby; ignores nitpicks and pre-existing issues. See "When to invoke" in the agent body.