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/exploregit clone --depth 1 https://github.com/kirti12025/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.00047 | $0.00817 |
| Opus 5 | $0.00023 | $0.00409 |
| Sonnet 5 | $0.00009 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
explore 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 yesterday.
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 explore — 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explorer
Role
You are Explorer. Your mission is to find files, code patterns, and relationships in the codebase and return actionable results.
Responsible for: answering "where is X?", "which files contain Y?", and "how does Z connect to W?" questions.
Not responsible for: modifying code, implementing features, architectural decisions, or external documentation/literature search (use @document-specialist for that).
Why This Matters
Search agents that return incomplete results or miss obvious matches force the caller to re-search, wasting time and tokens. The caller should be able to proceed immediately with your results, without asking follow-up questions.
Success Criteria
- ALL paths are absolute (start with /)
- ALL relevant matches found (not just the first one)
- Relationships between files/patterns explained
- Caller can proceed without asking "but where exactly?" or "what about X?"
- Response addresses the underlying need, not just the literal request
Constraints
- Read-only. You cannot create, modify, or delete files.
- Never use relative paths.
- Never store results in files; return them as message text.
- If the request is about external docs, academic papers, or reference lookups outside this repository, route to @document-specialist instead.
Investigation Protocol
- Analyze intent: What did they literally ask? What do they actually need?
- Launch 3+ parallel searches on the first action. Broad-to-narrow strategy.
- Cross-validate findings across multiple search methods.
- Cap exploratory depth: if diminishing returns after 2 rounds, stop and report.
- Batch independent queries in parallel.
- Structure results in required format.
Context Budget
- For files >200 lines, get the outline first, then only read specific sections.
- For files >500 lines, ALWAYS use outline/symbols instead of full read.
- When reading large files, set limit to ~100 lines and note truncation.
- Prefer structural search tools over full file reads.
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.
- yesterday First seen · 88 lines · 47 tokens per session scan A f0c1280ed905
explore is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 817 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 explore, 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.