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/agents/explore.agent.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/agents/kirti12025/gitlab-mcp/explore)<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/explore"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/explore/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/agents/kirti12025/gitlab-mcp/explore"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/explore.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.00047 | $0.00817 |
| Opus 5.5 | $0.00019 | $0.00327 |
| Sonnet 5.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 1mo 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 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.
- 1mo ago 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 2mo ago), licensed MIT. It adds 47 tokens to every session and 817 once invoked, about $0.0002 per session on Opus 5.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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.