Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritnpx agentmods add commands/boparaiamrit/skills-by-amrit/teamWrote 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/commands/boparaiamrit/skills-by-amrit/team)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/team"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/team/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/commands/boparaiamrit/skills-by-amrit/team"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/team.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.00017 | $0.01563 |
| Opus 5 | $0.00009 | $0.00781 |
| Sonnet 5 | $0.00003 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00156 |
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 12d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/team — Multi-Agent Council
Start and manage a council session where each specialist agent runs in its own fresh 200k context, coordinated through CLI commands and file-based handoffs.
Usage
/team [objective]— Start a new council session (auto-selects preset)/team [objective] --preset full— Start with a specific preset/team [objective] --auto— Run autonomously (skip confirmations, auto-handle gate failures)/team resume— Resume an existing council session/team board— Show current council task board/team status— Show council status and agent states
Protocol
Parse Arguments
Extract from $ARGUMENTS:
- objective: Everything that isn't a flag (required for
start, not forresume/board/status) - --preset: Council preset (
full,rapid,debug,architecture,refactoring,audit). Default: auto-select based on objective. - --auto: Autonomous mode — skip user confirmations, auto-retry on gate failures (once), auto-approve routing decisions.
Subcommand: resume
If first argument is "resume":
RESUME=$(node scripts/planning-tools.cjs council resume)
if [[ "$RESUME" == @file:* ]]; then RESUME=$(cat "${RESUME#@file:}"); fi
Parse JSON. Report where the session left off. Continue the workflow from execute_agent_sequence at the next uncompleted agent.
Subcommand: board
If first argument is "board":
node scripts/planning-tools.cjs council board
Display the board output. Done.
Subcommand: status
If first argument is "status":
STATUS=$(node scripts/planning-tools.cjs council status)
if [[ "$STATUS" == @file:* ]]; then STATUS=$(cat "${STATUS#@file:}"); fi
Display council status including: objective, preset, active agent, completed agents, remaining agents, message count, gate results. Done.
Starting a New Council
1. Validate objective:
If no objective provided, ask:
What do you want the council to work on?
Wait for response.
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.
- 12d ago First seen · 191 lines · 17 tokens per session scan A f09e425fdb27
team is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 1,563 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.