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 commands/ruizrica/toolkit/teamgit clone --depth 1 https://github.com/ruizrica/toolkitWhat 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.00000 | $0.00565 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/team
Coordinate a multi-agent team to implement features, code, or solutions in parallel. This command automatically analyzes tasks, decomposes them into parallel work streams, and spawns multiple specialized agents simultaneously.
Usage
/team [what to implement - feature/app/system/etc]
Arguments
| Argument | Required | Description |
|---|---|---|
| task description | Yes | What you want to implement (feature, app, system, etc.) |
How It Works
- Analyze - Parses the task and breaks it into parallel work streams
- Decompose - Creates 3-6 parallel sub-tasks based on the request
- Assign - Selects appropriate agent types for each sub-task
- Execute - Spawns multiple agents in parallel using a single response
- Synthesize - Collects results and combines them into a cohesive output
Available Agents
The /team command can spawn any of these specialized agents:
Investigation & Research:
- gemini-agent - Large codebase analysis, research, documentation, web search
- cursor-agent - Code review, refactoring analysis, test planning
Implementation:
- codex-agent - Complex algorithms, advanced features, sophisticated logic
- qwen-agent - Performance optimization, data structures, complex refactoring
- opencode-agent - API development, standard CRUD, cost-effective bulk generation
- groq-agent - Rapid prototyping, boilerplate, simple utilities
Example
/team Implement user authentication with OAuth support
This might spawn:
- gemini-agent to research OAuth best practices
- cursor-agent to analyze existing auth code
- codex-agent to design the auth architecture
- qwen-agent to implement the core OAuth flow
Key Behaviors
- Parallel Execution - Spawns all agents in a single message for maximum parallelism
- No Confirmation - Acts immediately without waiting for user confirmation
- Automatic Selection - Chooses the right agents based on task requirements
- Result Synthesis - Combines all agent outputs into a unified 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.
- 2d ago First seen · 73 lines · 0 tokens per session scan A bc6116cb9af6
team is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 tokens. 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.