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/zereight/gitlab-mcp/teamnpx skills add zereight/gitlab-mcp --skill teamgit clone --depth 1 https://github.com/zereight/gitlab-mcpWhat 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.00037 | $0.01488 |
| Opus 5 | $0.00018 | $0.00744 |
| Sonnet 5 | $0.00007 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team
Spawn N coordinated agents working on a shared task list. Uses VS Code's native subagent system for team management, inter-agent messaging, and task dependencies.
When to Use
- Task is decomposable into independent subtasks
- Multiple files/modules need parallel work
- Large-scale refactoring, migration, or multi-service work
When NOT to Use
- Single-file changes → use
/omg-autopilotor direct editing - Sequential pipeline → use
/omg-autopilot - Just need a plan → use
/planor/ralplan
Usage
/team 3:executor "fix all TypeScript errors"
/team 4:designer "implement responsive layouts"
/team "refactor the auth module"
/team ralph "build a complete REST API"
Parameters
- N — Number of agents (1-20). Defaults to auto-sizing.
- agent-type — Agent for
team-execstage (executor, debugger, designer, etc.). Defaults to stage-aware routing. - ralph — Wraps team in Ralph's persistence loop (retry on failure, verification before completion).
- task — High-level task to decompose and distribute.
Architecture
User: "/team 3:executor fix all TypeScript errors"
|
v
[omg-coordinator (Lead)]
|
+-- Analyze & decompose → subtask list
|
+-- Create tasks with dependencies
|
+-- Spawn N worker agents (subagents)
|
+-- Monitor loop (messages + task polling)
|
+-- Completion → shutdown workers → cleanup
Staged Pipeline
team-plan → team-prd → team-exec → team-verify → team-fix (loop)
Stage Agent Routing
Each stage uses specialized agents — not just executors:
| Stage | Required Agents | Optional Agents |
|---|---|---|
| team-plan | @explore, @planner | @analyst, @architect |
| team-prd | @analyst | @critic |
| team-exec | @executor | @debugger, @designer, @writer, @test-engineer |
| team-verify | @verifier | @test-engineer, @security-reviewer, @code-reviewer |
| team-fix | @executor | @debugger |
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 · 185 lines · 37 tokens per session scan A ec573de6bd9a
team is a skill published in the GitHub repository zereight/gitlab-mcp (1,939 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,488 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-30.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
add-resend
Add Resend (email) channel integration via Chat SDK.
codegen
Code generation utilities for json-render. Use when generating code from UI specs, building custom code exporters, traversing specs, or serializing props for @json-render/codegen.
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…