Borrowing it
Nothing to install: this file belongs to kirti12025/gitlab-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kirti12025/gitlab-mcp/custom-tool-pipeline-summary/.github/skills/team/SKILL.mdgit clone --depth 1 https://github.com/kirti12025/gitlab-mcpWrote 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/kirti12025/gitlab-mcp/team)<a href="https://agentmods.dev/skills/kirti12025/gitlab-mcp/team"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/team.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.1 | $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 7d 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.
This is a copy
100% identical to team — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 7d ago First seen · 185 lines · 37 tokens per session scan A ec573de6bd9a
team is a skill published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo ago), 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. It is 100% identical to team, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…