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/joelmnz/mcp-markdown-manager/code-reviewnpx skills add joelmnz/mcp-markdown-manager --skill code-reviewgit clone --depth 1 https://github.com/joelmnz/mcp-markdown-managerWrote 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/joelmnz/mcp-markdown-manager/code-review)<a href="https://agentmods.dev/skills/joelmnz/mcp-markdown-manager/code-review"><img src="https://agentmods.dev/badge/skills/joelmnz/mcp-markdown-manager/code-review.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.00019 | $0.01315 |
| Opus 5 | $0.00010 | $0.00658 |
| Sonnet 5 | $0.00004 | $0.00263 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
code-review 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I Do
Enforce AGENTS.md rules during PR review (architecture layering, TypeScript discipline, DB safety, auth, MCP protocol, tests).
Core Checklist (Must Enforce)
Architecture / Boundaries
- Layering: Routes/Handlers (
routes/) → Service Facade (services/articles.ts) → DB Services (databaseArticles.ts,databaseVersionHistory.ts,databaseEmbedding.ts) → PostgreSQL - Single server:
src/backend/server.tshandles API, MCP, and static serving - Routes = orchestration only (auth check → validate input → call service → format response)
- Services throw descriptive errors; handlers catch and return HTTP status codes
- Use the facade: handlers call
articleService, never import DB services directly - Filenames are virtual:
slug+.md(useslugToFilename/filenameToSlug)
TypeScript / Imports (CRITICAL)
- Strict mode: no
any, no@ts-ignore, no@ts-expect-error - Explicit interfaces for all data structures
- ESM only with
.tsextensions in imports (e.g.,from './file.ts') - Node built-ins via bare specifiers (
fs/promises,path) - Naming:
camelCasefunctions/vars,PascalCaseComponents/Interfaces,SCREAMING_SNAKE_CASEconstants - If you see type suppression: block the review until fixed
Database Operations
- Parameterized queries only (
$1, $2placeholders) — never string interpolation in SQL - Connection pooling: use
databaseService.getClient(), never createPoolinstances - Always
client.release()infinallyblocks — no resource leaks - Wrap DB operations in try-catch, use
handleDatabaseError()
Authentication & Security
- All write endpoints:
requireAuth(request, 'write')with scope check - All read endpoints:
requireAuth(request)(read-only scope minimum) - Web-only endpoints (token management):
useWebAuth: true - Bearer tokens:
Authorization: Bearer <token>— never log full tokens - Input validation via
mcp/validation.tshelpers - Path traversal prevention (no
../in filenames/slugs) - DOMPurify for user content on frontend
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 · 118 lines · 19 tokens per session scan A 3c94adbec7fd
code-review is a skill published in the GitHub repository joelmnz/mcp-markdown-manager (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,315 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…