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 instructions/joelmnz/mcp-markdown-manager/agents-mdgit 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/instructions/joelmnz/mcp-markdown-manager/agents-md)<a href="https://agentmods.dev/instructions/joelmnz/mcp-markdown-manager/agents-md"><img src="https://agentmods.dev/badge/instructions/joelmnz/mcp-markdown-manager/agents-md.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.00792 | $0.00792 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
mcp-markdown-manager AGENTS.md 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for MCP Markdown Manager
Commands
- Install:
bun install(install dependencies, run after git checkout or after adding new dependencies) - Build:
bun run build(builds frontend with hashed assets) - Typecheck:
bun run typecheck(run this after changes) - Dev:
bun run dev:backend(backend) andbun run dev:frontend(frontend, separate terminals) - Docker:
bun run dc:db- Start the database for local testingbun run dc:ui- Quick start (down, build, up in one command)docker compose down- Stop containers, run when you're done testing.docker logs mcp-markdown-manager- View backend logs
- Tests: No formal test runner. Run individual scripts in
scripts/:bun scripts/test-parsing.ts- Markdown parsingbun scripts/test-import.ts- Import functionalitybun scripts/test-error-handling.ts- DB error handlingbun scripts/test-api-client-runtime.ts- API Client testsbun scripts/verify-mcp.ts <AUTH_TOKEN>- MCP server integration test (requires server running)
Verification Strategy
When Build/Typecheck Fails
- Dependency issues (
Cannot findorMaybe you need to 'bun install'):- Run
bun installfirst, then retry verification
- Run
- Backend-only changes: Use
bun run dev:backendto verify syntax without frontend deps - Frontend broken: Backend changes can still be verified independently
Verification Methods (in order of preference)
- Automated:
bun run typecheck(requires deps installed) - Backend runtime:
bun run dev:backend(starts server, verifies syntax) - MCP integration:
bun run dev:backend # Terminal 1 bun scripts/verify-mcp.ts <TOKEN> # Terminal 2 - Manual code review (fallback):
- Check matching braces/parentheses
- Verify TypeScript type compatibility in changed sections
- Look for similar patterns elsewhere in codebase for reference
Pre-Commit Checklist
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 · 60 lines · 792 tokens per session scan A 26ece656a96d
mcp-markdown-manager AGENTS.md is an instructions file published in the GitHub repository joelmnz/mcp-markdown-manager (2 stars, last pushed 3mo ago), licensed MIT. It adds 792 tokens to every session, about $0.0040 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.