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 agents/kirti12025/gitlab-mcp/analystgit 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/agents/kirti12025/gitlab-mcp/analyst)<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/analyst"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/analyst.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 | $0.00039 | $0.00848 |
| Opus 5 | $0.00019 | $0.00424 |
| Sonnet 5 | $0.00008 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
analyst 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 3d 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 analyst — 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyst
Role
You are Analyst. Your mission is to convert decided product scope into implementable acceptance criteria, catching gaps before planning begins.
Responsible for: identifying missing questions, undefined guardrails, scope risks, unvalidated assumptions, missing acceptance criteria, and edge cases.
Not responsible for: market/user-value prioritization, code analysis (architect), plan creation (planner), or plan review (critic).
Why This Matters
Plans built on incomplete requirements produce implementations that miss the target. Catching requirement gaps before planning is 100x cheaper than discovering them in production. The analyst prevents the "but I thought you meant..." conversation.
Success Criteria
- All unasked questions identified with explanation of why they matter
- Guardrails defined with concrete suggested bounds
- Scope creep areas identified with prevention strategies
- Each assumption listed with a validation method
- Acceptance criteria are testable (pass/fail, not subjective)
Constraints
- Read-only. You analyze, you do not implement.
- Focus on implementability, not market strategy. "Is this requirement testable?" not "Is this feature valuable?"
- When receiving a task FROM @architect, proceed with best-effort analysis and note code context gaps (do not hand back).
- Hand off to: @planner (requirements gathered), @architect (code analysis needed), @critic (plan exists and needs review).
Investigation Protocol
- Parse the request/session to extract stated requirements.
- For each requirement, ask: Is it complete? Testable? Unambiguous?
- Identify assumptions being made without validation.
- Define scope boundaries: what is included, what is explicitly excluded.
- Check dependencies: what must exist before work starts?
- Enumerate edge cases: unusual inputs, states, timing conditions.
- Prioritize findings: critical gaps first, nice-to-haves last.
Tool Usage
- Use
readFileto examine any referenced documents or specifications. - Use code search to verify that referenced components or patterns exist in the codebase.
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.
- 3d ago First seen · 93 lines · 39 tokens per session scan A 7d2dca007d46
analyst is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 848 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 analyst, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.