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/update-project-documentationnpx skills add jmrplens/gitlab-mcp-server --skill update-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/update-project-documentation)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/update-project-documentation"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/update-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.00040 | $0.01365 |
| Opus 5 | $0.00020 | $0.00682 |
| Sonnet 5 | $0.00008 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
update-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 4d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Project Documentation
Primary Directive
Update existing documentation in the docs/ directory to reflect current source code changes. Perform a delta analysis between the implementation and documentation, then surgically update only the affected sections while preserving the overall document structure, style, and formatting.
Execution Context
This skill is triggered after code changes to ensure documentation stays in sync. It focuses on efficiency — only updating what has changed rather than regenerating entire documents.
Analysis Phase
Step 1: Identify Changed Code
- Check recent changes using git diff or by examining the files provided
- If no specific files are indicated, scan all Go source files for modifications
- Build a list of changed exported types, functions, constants, and configurations
- Identify new, modified, or removed public APIs
Step 2: Map Changes to Documentation
For each code change, identify which documentation files are affected:
| Change Type | Affected Documentation |
|---|---|
| New exported type/function | Package docs, possibly tools/resources reference |
| Modified function signature | Package docs, tools reference, examples |
| New MCP tool | docs/reference/tools/README.md, package docs |
| New MCP resource | docs/reference/resources.md, package docs |
| New MCP prompt | docs/reference/prompts.md, package docs |
| Configuration change | docs/reference/configuration.md |
| New package | docs/README.md index, new package doc |
| Architecture change | docs/concepts/architecture.md, diagrams |
| Build/deploy change | docs/development/development.md, docs/deployment.md |
| Removed API | All referencing documents |
Step 3: Assess Impact
For each affected document:
- Read the current documentation
- Compare with the current source code
- Classify the update as: Minor (parameter change), Moderate (new section), or Major (restructure)
- Prioritize Critical and High priority documents 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.
- 4d ago First seen · 150 lines · 40 tokens per session scan A f95fd1aa0e74
update-project-documentation is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (33 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,365 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
kayba-stage-1-api-analysis
Fetch pre-computed insights from the Kayba API and build a structured summary. Does NOT upload traces or trigger generation — analysis is assumed to already exist. Trigger when the user says "run stage 1", "get insights", "fetch skills", "kayba analyze", or when invoked by the kayba-pipeline orchestrator. Requires the…