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 skills add LuuOW/meridian-mcp --skill docs-updategit clone --depth 1 https://github.com/LuuOW/meridian-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/skills/luuow/meridian-mcp/docs-update)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/docs-update"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/docs-update.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.1 | $0.00046 | $0.01886 |
| Opus 5 | $0.00023 | $0.00943 |
| Sonnet 5 | $0.00009 | $0.00377 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
docs-update 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 6d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-update
How to get productive in an unfamiliar (or returning) codebase as fast as possible by reading structured documentation before touching any code. Also covers keeping docs current so the next session costs fewer tokens.
1) The MD-First Orientation Protocol
When entering a repo cold, read docs in this order — stop as soon as you have enough context for the task:
1. README.md ← what the project is, how to run it
2. ARCHITECTURE.md ← system topology, agent/service boundaries
3. PENDING.md ← what's disabled, what's blocked, what's planned
4. CLAUDE.md ← AI-specific instructions and constraints
5. docs/*.md ← deep dives on specific subsystems
6. CHANGELOG.md ← what changed recently (last 5 entries)
7. <subdir>/README.md ← module-level context (check if it exists)
Read code only when docs leave a specific question unanswered.
# Find all .md files in the repo (sorted by size — larger = more useful)
find /opt/myrepo -name "*.md" -not -path "*node_modules*" -not -path "*.git*" \
| xargs wc -l 2>/dev/null | sort -rn | head -20
2) What Each Doc Type Reveals
| File | What to extract |
|---|---|
README.md |
Stack, quick-start commands, port numbers, env setup |
ARCHITECTURE.md |
Service names, data flows, which agent does what |
PENDING.md |
Disabled features (don't fix what's intentionally off), blockers, credentials needed |
CLAUDE.md |
Constraints the AI must follow, naming conventions, off-limits areas |
CHANGELOG.md |
Recent breakage, recently added features, migration notes |
.env.example |
Every external dependency (API keys = external services used) |
Makefile |
Runnable commands the team actually uses day-to-day |
docker-compose.yml |
Services, ports, volumes — the runtime topology |
package.json / pyproject.toml |
Exact dependencies and versions |
pytest.ini / vitest.config.ts |
How tests are structured and run |
3) Targeted Follow-Up Questions After Reading Docs
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.
- 6d ago First seen · 191 lines · 46 tokens per session scan A f509152e5833
docs-update is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,886 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-31.
Other skills, from other repositories
docs-page
A long-form technical documentation page with a left navigation panel, a main article, and a right table of contents. A table of contents lists the page sections and links to them.
codebase-to-course
Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a…
doc-kami-parchment
Warm parchment canvas (#f5f4ed), monochrome ink-blue accent (#1B365D), one serif family, and editorial-grade typography.
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
eng-runbook
A template for an engineering runbook, which is a practical guide engineers use during service operation and on-call incidents.
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.