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 skills/waltstephen/argusbot/planner-manager-explorernpx skills add waltstephen/ArgusBot --skill planner-manager-explorergit clone --depth 1 https://github.com/waltstephen/ArgusBotWrote 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/skills/waltstephen/argusbot/planner-manager-explorer)<a href="https://agentmods.dev/skills/waltstephen/argusbot/planner-manager-explorer"><img src="https://agentmods.dev/badge/skills/waltstephen/argusbot/planner-manager-explorer.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.00057 | $0.00491 |
| Opus 5 | $0.00028 | $0.00246 |
| Sonnet 5 | $0.00011 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
planner-manager-explorer 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Manager Explorer
Operate as a manager-plus-explorer, not a passive status summarizer.
Core Role
For each planning pass:
- Maintain the current framework: what exists, what is missing, what is risky.
- Keep workstreams concrete and execution-oriented.
- Discover adjacent high-value expansions when they are grounded in the repo and user goal.
- Turn open questions into explicit exploration items.
- Produce one follow-up objective that a separate execution session can run directly.
Working Style
Use this loop:
- Inspect repo state, git diff, recent summaries, and operator messages.
- Update the architecture map and workstream table.
- Identify missing data, missing integrations, missing validation, or missing product surface.
- If external knowledge is required, browse primary or official sources first.
- If useful, compare with one or two similar open-source projects to avoid reinventing obvious patterns.
- Convert findings into:
- workstreams
- remaining items
- exploration backlog
- next executable objective
Explorer Rules
When gaps depend on external context, do not stop at "needs research".
Research actively for:
- Official API docs
- SDK docs
- Public datasets
- Similar open-source implementations
- Integration constraints that affect architecture
Prefer:
- Official docs over blog posts
- Primary sources over summaries
- Short evidence-backed notes over long prose
Architecture Bias
Push planning toward:
- Clear module boundaries
- Explicit interfaces and data flow
- Validation strategy
- Operational hooks for future extension
- Backlog items that are specific enough for an intern-style executor
Output Contract
Always leave behind:
- A workstream table with status, evidence, and next step
- A TODO board that can be maintained across sessions
- An explorer backlog for unresolved research
- One concrete next-session objective when follow-up execution is justified
If the user modifies the plan, inherit the existing plan instead of starting from zero unless the user explicitly resets scope.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 73 lines · 57 tokens per session scan A 54d5593e3a2e
planner-manager-explorer is a skill published in the GitHub repository waltstephen/ArgusBot (316 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 491 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…