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 skills/jmrplens/gitlab-mcp-server/generate-project-documentationnpx skills add jmrplens/gitlab-mcp-server --skill generate-project-documentationgit clone --depth 1 https://github.com/jmrplens/gitlab-mcp-serverWrote 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/jmrplens/gitlab-mcp-server/generate-project-documentation)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-project-documentation"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/generate-project-documentation.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.00043 | $0.02151 |
| Opus 5 | $0.00022 | $0.01076 |
| Sonnet 5 | $0.00009 | $0.00430 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
generate-project-documentation 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Project Documentation
Primary Directive
Generate comprehensive, well-organized documentation for the project. Analyze the entire codebase and produce a complete documentation suite covering architecture, components, APIs, developer guides, and deployment configuration.
The documentation must be:
- Accurate (absolute parity with source code)
- Organized (Diátaxis framework: Tutorials, How-to, Reference, Explanation)
- Navigable (index with cross-references between documents)
- Visual (Mermaid diagrams for architecture and data flow)
- Self-contained (no external context required to understand)
Execution Context
This skill is designed for the Documentation Writer agent or any agent tasked with producing project documentation. All output must be in English per the project language policy.
Analysis Phase
Before generating any documentation, complete a thorough analysis:
Step 1: Repository Structure Discovery
- Explore the complete project directory structure
- Identify all Go packages and their responsibilities
- Map the dependency graph between internal packages
- Locate existing documentation and assess gaps
- List all configuration files, build scripts, and CI/CD pipelines
Step 2: Architecture Understanding
- Read the entry point (
cmd/server/main.go) to understand initialization flow - Identify the configuration loading mechanism
- Map how the GitLab client is initialized and injected
- Understand the MCP server setup and tool registration pattern
- Trace a complete request flow from MCP client to GitLab API and back
Step 3: API Surface Inventory
- List all MCP tools with their input/output types
- List all MCP resources with their URI templates
- List all MCP prompts with their parameters
- Document pagination patterns and shared types
- Identify tool annotations (readOnlyHint, destructiveHint, etc.)
Step 4: Gap Analysis
- Compare current documentation against the coverage matrix below
- Identify missing, outdated, or incomplete documentation
- Prioritize generation of missing critical documentation first
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.
- 5d ago First seen · 284 lines · 43 tokens per session scan A 589355d136f8
generate-project-documentation is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (33 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 2,151 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 skills, from other repositories
latex-compile
Compile a LaTeX document and fix every error plus aesthetic issue (overfull/underfull boxes, widows, alignment, fonts) for a clean PDF and log. Use this instead of running pdflatex/latexmk manually — it avoids the latexmk stale-log trap and silent grep failures on binary log output, and it reformats rather than…
sync-brief
Propagate load-bearing changes from workbook.tex to brief.tex.
llm-docs-generator
Operating playbook for generating and maintaining version-pinned documentation packs with the llm-docs CLI. Use when building, refreshing, or verifying an agent-ready docs pack for a specific installed library version, or when maintaining this repository.
python-executor
Execute Python code in a safe sandboxed environment via inference.sh. Pre-installed: NumPy, Pandas, Matplotlib, requests, BeautifulSoup, Selenium, Playwright, MoviePy, Pillow, OpenCV, trimesh, and 100+ more libraries. Use for: data processing, web scraping, image manipulation, video creation, 3D model processing, PDF…
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.…
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…