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/teamnpx skills add xWael9/ClaudeBoss --skill teamgit 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/team)<a href="https://agentmods.dev/skills/xwael9/claudeboss/team"><img src="https://agentmods.dev/badge/skills/xwael9/claudeboss/team.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.00059 | $0.00601 |
| Opus 5 | $0.00030 | $0.00300 |
| Sonnet 5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
team 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClaudeBoss — Team Mode
You (Claude Code) and a free opencode agent work as a pair on one task. Opencode does the first pass; you review it like a second engineer would, then implement/finish it yourself.
Drift-prone. Free model catalogs (OpenCode Zen, OpenRouter) change without notice. Model selection happens live via
opencode modelsevery run — never assume a specific model id still exists.
Prerequisites
Run once per machine: claudeboss install — checks/installs the opencode CLI, verifies a free model is reachable, and prints manual OpenRouter fallback steps if not (no automated account creation, by design).
Workflow
-
Classify the task into one of:
code,write,research,general(use/claudeboss:planinstead, first, if the task itself is "figure out the right approach"). Coding tasks (features, fixes, refactors) →code. Prose/docs/copy →write. Fact-finding/comparison →research. Anything else →general. -
Delegate. Run:
claudeboss run <task-type> "<precise task description — same detail you'd give a human contractor>"This is a blocking call — wait for it to return, don't poll.
-
Review the output like a code review, not a rubber stamp. Check:
- Does it actually satisfy the request, not just look plausible?
- Correctness — run tests/typecheck/lint if applicable, read the actual diff, don't trust a summary of it.
- Fit with the existing codebase's conventions.
-
Implement. You apply the result yourself — edit files with Edit/Write, run verification (tests, the
runskill, a browser check for UI), and fix anything opencode got wrong or left incomplete. Treat its output as a first draft from a teammate, not a final answer. -
If opencode's draft is unusable (wrong approach, missed the point), don't loop forever — after 2 failed delegations, tell the user directly and offer to just do the task yourself. Free models are weaker than you; don't over-trust them on hard problems.
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 · 40 lines · 59 tokens per session scan A acab18d0195e
team is a skill published in the GitHub repository xWael9/ClaudeBoss (2 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 601 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.