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/status/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/status)<a href="https://agentmods.dev/skills/kirti12025/gitlab-mcp/status"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/status/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/kirti12025/gitlab-mcp/status"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/status.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.00037 | $0.00481 |
| Opus 5.5 | $0.00015 | $0.00192 |
| Sonnet 5.5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
status 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 2mo 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 status — 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.
What it actually says
Status
Show the current state of all OMG modes, active agents, and progress.
When to Use
- Check what mode is currently active
- See progress of omg-autopilot, ralph, or team execution
- Verify state after a cancel or resume
Workflow
1. Scan State Files
Read .omc/state/ directory for active mode state files:
omg-autopilot-state.jsonralph-state.jsonultrawork-state.jsonultraqa-state.jsonteam-state.jsonself-improve/state/agent-settings.json
2. Report Active Modes
For each active mode, show:
OMG Autopilot:
- Current phase (0-5)
- Phase name and progress
- Files modified so far
Ralph:
- Current story (N of M)
- Stories passing / total
- Linked ultrawork status
Team:
- Team name and member count
- Current pipeline stage
- Task completion (N/M tasks done)
UltraQA:
- Current cycle (N of 5)
- Last failure summary
Self-Improve:
- Current iteration
- Best score vs baseline
- Improvement percentage
- Stop condition proximity
3. Report No Active Modes
If nothing is active: "No active OMG modes. Start with /omg-autopilot, /ralph, or /team."
Output Format
=== OMG Status ===
Mode: OMG Autopilot
Phase: 2/5 (Execution)
Started: 2 minutes ago
Files modified: 12
Mode: Team (linked)
Team: fix-ts-errors
Stage: team-exec
Workers: 3/3 active
Tasks: 2/5 completed
Verbose Mode (--verbose)
With --verbose, also show:
- Full state JSON for each active mode
- Recent git log (last 5 commits)
.omc/directory listing
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.
- 2mo ago First seen · 85 lines · 37 tokens per session scan A 5852fdb87cd6
status is a skill published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 481 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to status, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…