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 skills add CodeInfinity1/Stram --skill agent-team-orchestrationgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/agent-team-orchestration)<a href="https://agentmods.dev/skills/codeinfinity1/stram/agent-team-orchestration"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/agent-team-orchestration/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/skills/codeinfinity1/stram/agent-team-orchestration"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/agent-team-orchestration.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.00042 | $0.00632 |
| Opus 5.5 | $0.00017 | $0.00253 |
| Sonnet 5.5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
agent-team-orchestration 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Orchestration
Purpose
Break complex work into specialist tasks while preserving a single accountable orchestrator. This adapts external reference team orchestration and external reference kanban-orchestrator concepts into Stram's multi-agent coordination board.
When To Use
Use for large engineering changes, research plus implementation, security review, UI plus backend tasks, or any goal requiring multiple roles and verifiable handoffs.
Inputs And Evidence
- User objective and success criteria.
- Current capability surface and available specialists.
- Existing task board and active commitments.
- Risk/approval boundaries.
Tool Map
multi_agent_coordinatemulti_agent_boardcognitive_statecognitive_priority_reviewcodex_cli_plancodex_cli_runwrite_note
Workflow
- Define the shared goal and completion evidence.
- Split work into small tasks with owner/role, input evidence, expected output, and verification.
- Use
multi_agent_coordinateto record a board when the task set is non-trivial. - Delegate to external workers only after model-led delegation planning and approval policy review.
- Require each worker output to be verified locally.
- Merge results into one final answer with unresolved risks and next actions.
Safety And Boundaries
- Do not delegate secrets or broad write access unnecessarily.
- Treat worker output as evidence, not truth.
- Do not let parallel work overwrite user changes.
Safety And Approval
- Delegate only bounded tasks with explicit workspace, allowed files, expected outputs, and verification.
- Require approval before external workers run commands, modify files, call live services, push, deploy, or access secrets.
- Keep one accountable orchestrator responsible for reviewing worker output and protecting user changes.
- Pause coordination if workers conflict, produce unverifiable claims, or require credentials/user decisions.
Native Implementation Boundaries
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 · 78 lines · 42 tokens per session scan A 2edf13e793e7
agent-team-orchestration is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 632 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
product-management
Product management expertise for product strategy, roadmap planning, feature prioritization (RICE, ICE, MoSCoW), customer research, A/B testing, product analytics, and product-market fit. Use when building product roadmaps, prioritizing features, or defining product strategy.
init-project
Bootstrap a new research project. Interview for details, scaffold directory structure, create Overleaf symlink, initialise git, and create project context files.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
setup
Interactive onboarding that discovers team structure, terminology, development goals, performance and management frameworks, organizational values, and ways of working by crawling Slack, Notion, Google Drive, Gmail, and Calendar. Validates everything with the manager before persisting. Run this first before using any…
workspace
Scaffold and manage the stateless AI workspace — context, packs, repos, and knowledge for multi-repo orchestration.