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/xwael9/claudeboss/plannpx skills add xWael9/ClaudeBoss --skill plangit clone --depth 1 https://github.com/xWael9/ClaudeBossWrote 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/xwael9/claudeboss/plan)<a href="https://agentmods.dev/skills/xwael9/claudeboss/plan"><img src="https://agentmods.dev/badge/skills/xwael9/claudeboss/plan.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.00054 | $0.00466 |
| Opus 5 | $0.00027 | $0.00233 |
| Sonnet 5 | $0.00011 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
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 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
ClaudeBoss — Plan Mode
Opencode ships a dedicated plan primary agent, separate from build. Use it when the task is "figure out the right approach" rather than "write the code" -- it's a distinct pass from /claudeboss:team and /claudeboss:boss, meant to run before either of them on non-trivial work.
Prerequisites
claudeboss install must have succeeded at least once on this machine.
Workflow
-
Delegate the planning question, not the implementation:
claudeboss run plan "<the design question: what needs to change, what constraints apply, what are the tradeoffs>"claudeboss run planautomatically routes to opencode'splanagent (notbuild) and a general-purpose free model. -
Review the plan like you'd review a design doc. Does it account for the actual codebase's conventions and constraints (you may need to check the real code yourself -- the free model has no memory of this specific project beyond what you told it)? Is it missing an edge case, a migration step, a rollback path?
-
Hand off. Once the plan is sound, either:
- implement it yourself,
- delegate implementation to
/claudeboss:team(you review + finish), or - delegate to
/claudeboss:boss(you manage, opencode'sbuildagent implements, you approve before deploy).
Tell the user which handoff you're using and why.
-
If the plan is weak (vague, ignores a stated constraint, unworkable), don't pass it downstream -- refine the prompt and re-run, or just write the plan yourself and say so. A bad plan compounds into worse code if it flows straight into
/claudeboss:boss.
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 · 34 lines · 54 tokens per session scan A 1b29420166fa
plan is a skill published in the GitHub repository xWael9/ClaudeBoss (2 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 466 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-31.
Other skills, from other repositories
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.