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/josix/agent-flow/team-decisionnpx skills add josix/agent-flow --skill team-decisiongit clone --depth 1 https://github.com/josix/agent-flowWrote 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/josix/agent-flow/team-decision)<a href="https://agentmods.dev/skills/josix/agent-flow/team-decision"><img src="https://agentmods.dev/badge/skills/josix/agent-flow/team-decision.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 | $0.00039 | $0.02030 |
| Opus 5 | $0.00019 | $0.01015 |
| Sonnet 5 | $0.00008 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
team-decision 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 4d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Decision
Overview
The team decision skill guides the choice between parallel Agent Teams execution and sequential subagent orchestration. This skill analyzes task characteristics to determine whether parallel execution is safe, beneficial, and cost-effective.
Owner Agent: Senku (Planner Agent)
Consumers: Orchestrator (primary decision maker)
Key Principles
- Safety First: Only parallelize when tasks are truly independent
- Cost-Benefit Analysis: Parallel overhead must be justified by time savings
- File Ownership: Exclusive file ownership prevents conflicts
- Fail to Sequential: When in doubt, use sequential orchestration
When to Use This Skill
Apply team decision analysis when:
- A task naturally decomposes into multiple subtasks
- Subtasks could potentially run in parallel
- Time-to-completion is a priority
- Determining whether to spawn a team or orchestrate sequentially
Decision Criteria Table
| Criterion | Use Teams (Parallel) | Use Sequential |
|---|---|---|
| Task Independence | No shared state or files | Tasks have dependencies |
| File Ownership | Exclusive file sets | Overlapping file sets |
| Parallelism Safety | Safe or Moderate | Risky |
| Number of Tasks | 2-4 independent tasks | 1 task or 5+ tasks |
| Time Sensitivity | High (user waiting) | Low (can afford serial) |
| Coordination Cost | Low (simple merge) | High (complex merge) |
| Risk Tolerance | High (can retry) | Low (must be correct) |
Quick Decision Flowchart
Task Decomposition Available?
|
+-- NO --> Sequential (single agent)
|
+-- YES
|
v
Subtasks Share Files?
|
+-- YES --> Sequential (conflict risk)
|
+-- NO
|
v
Subtasks Have Dependencies?
|
+-- YES --> Sequential (ordering required)
|
+-- NO
|
v
2-4 Subtasks?
|
+-- NO --> Sequential (too few or too many)
|
+-- YES
|
v
Time Savings > Overhead?
|
+-- YES --> TEAMS (Parallel)
|
+-- NO --> Sequential
What ships with it
3 files 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.
- 4d ago First seen · 303 lines · 39 tokens per session scan A 48f866ab381d
team-decision is a skill published in the GitHub repository josix/agent-flow (7 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 2,030 once invoked, about $0.0002 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
pandic-office
Convert Markdown to PDF (or DOCX/EPUB/HTML) using the pandoc CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file.
tmux
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).
ship-and-babysit
End-to-end PR shipping workflow for tinyhumansai/openhuman: commit local changes, push to the user's fork, open or reuse a PR against main, then babysit CI and CodeRabbit feedback until the PR is green and clean. Use when the user asks to ship, open a PR, monitor CI, address review comments, or 'babysit' a branch.
shogun-screenshot
スクリーンショットの取得・加工を行う。ローカルスクショから最新画像を取得、 PlaywrightでWebページをキャプチャ、画像のトリミング・リサイズ、機微情報を黒塗りマスキング。 記事執筆、レポート作成、UI確認、画像加工時に起動。 「スクショ」「スクリーンショット」「画面キャプチャ」「最新のスクショ」「画像加工」「トリミング」「マスク」「写メ」「写メ撮った」「スクショ撮った」で起動。 Do NOT use for: 画像生成(shogun-imagegenを使え)。.
web-research
Use this skill for requests related to web research; it provides a structured approach to conducting comprehensive web research.
story-long-write
长篇网文写作方法论与 novel-studio pipeline 适配器。用于把长篇开书、大纲、日更、续写、重写等需求整理为 pipeline 输入;在 novel-studio 内禁止直接生成正文。触发方式:/story-long-write、/写长篇、「帮我开书」「写大纲」「日更」「续写」「继续写」「修改第X章」「回炉」「重写第X章」。.