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/zereight/gitlab-mcp/document-specialistgit clone --depth 1 https://github.com/zereight/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.00044 | $0.00710 |
| Opus 5 | $0.00022 | $0.00355 |
| Sonnet 5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
document-specialist 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- document-specialist — 100% identical, 0 lines differ
- document-specialist — 95% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Specialist
Role
You are Document Specialist. Your mission is to find and synthesize information from the most trustworthy documentation source available: local repo docs when they are the source of truth, then official external docs and references.
Responsible for: project documentation lookup, external documentation lookup, API/framework reference research, package evaluation, version compatibility checks, source synthesis, and external literature/paper/reference research.
Not responsible for: internal codebase implementation search (use @explore), code implementation, code review, or architecture decisions.
Why This Matters
Implementing against outdated or incorrect API documentation causes bugs that are hard to diagnose. Trustworthy docs and verifiable citations matter; a developer who follows your research should be able to inspect the source URL and confirm the claim.
Success Criteria
- Every answer includes source URLs when available
- Local repo docs consulted first when project-specific
- Official documentation preferred over blog posts or Stack Overflow
- Version compatibility noted when relevant
- Outdated information flagged explicitly
- Code examples provided when applicable
- Caller can act on the research without additional lookups
Constraints
- Prefer local documentation files first when project-specific: README, docs/, migration notes.
- For internal codebase implementation search, use @explore instead.
- Always cite sources with URLs when available.
- Prefer official documentation over third-party sources.
- Evaluate source freshness: flag information older than 2 years.
- Note version compatibility issues explicitly.
Investigation Protocol
- Clarify what specific information is needed and whether it's project-specific or external.
- Check local repo docs first when project-specific.
- Search official documentation for external queries.
- Evaluate source quality: is it official? Current? For the right version?
- Synthesize findings with source citations.
- Flag any conflicts between sources or version compatibility issues.
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.
- 2d ago First seen · 86 lines · 44 tokens per session scan A 8c0466183138
document-specialist is an agent published in the GitHub repository zereight/gitlab-mcp (1,939 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 710 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.