Borrowing it
Nothing to install: this file belongs to masaki39/marp-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/masaki39/marp-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/masaki39/marp-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/instructions/masaki39/marp-mcp/claude-md)<a href="https://agentmods.dev/instructions/masaki39/marp-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/masaki39/marp-mcp/claude-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.1 | $0.01049 | $0.01049 |
| Opus 5 | $0.00524 | $0.00524 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
marp-mcp CLAUDE.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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — 開発エッセンス
ドキュメント自動生成(最重要)
README.md、skills/marp/SKILL.md、assets/examples/md/はすべて Jest テスト内で自動生成されるpnpm testを実行すると上書きされるため、内容を変えたい場合は対応する generator テストを修正する- README →
src/__tests__/readme-generator.test.ts - SKILL.md →
src/__tests__/skill-generator.test.ts - Examples →
src/styles/__tests__/example-generator.test.ts、src/themes/__tests__/example-generator.test.ts
- README →
.claude/skills/marp/SKILL.mdはskills/marp/SKILL.mdへのシンボリックリンク- generator テストも
pnpm testに含まれるため、テスト実行 = ドキュメント再生成
ESM + TypeScript
"type": "module"プロジェクト。import は必ず.js拡張子をつける(import { foo } from "./bar.js")- ビルド:
tsc→build/に出力
ツール追加パターン
src/tools/{name}.tsに Zod スキーマ + async ハンドラsrc/mcp.tsでserver.tool(name, description, schema.shape, handler)—.shapeを渡すことsrc/cli/commands.tsに CLI サブコマンド追加- レスポンスは
createErrorResponse()/createSuccessResponse()(src/utils/response.ts)を使う
テーマ・スタイル追加パターン
- テーマ:
src/themes/{name}/index.tsでThemeDefinitionをエクスポート →src/themes/index.tsのthemesに登録 - スタイル:
src/styles/{name}/index.ts+css.ts→src/styles/index.tsのstylesに登録 - スタイルのレイアウトは同名のテーマレイアウトをオーバーライドする
- 追加後は generator テストのサンプルパラメータも追加すること
スライド分割
splitSlides()(src/utils/frontmatter.ts)を必ず使う。正規表現を直接書かないこと
Marp 画像モーフィング(CSS View Transitions)
は CSSbackground-imageになるため DOM の<img>がなくview-transition-nameが効かない- フルスクリーン画像は
<!-- _class: img-fullscreen -->+ inlineパターンを使う - alt の非キーワード語はそのまま HTML
alt属性になる →img[alt~="name"]で両スライドをターゲットできる
テスト規約
- 一時ディレクトリ:
fs.mkdtemp(path.join(os.tmpdir(), "marp-{prefix}-")) beforeEachでsetActiveTheme("default")を呼んでテーマ状態リセット
パッケージ管理 (pnpm)
- パッケージマネージャーは pnpm(
pnpm installでロックファイルpnpm-lock.yamlを更新) npm publish/npm versionは pnpm プロジェクトでもそのまま動作する"files":build,.claude/skills,README.md,LICENSEのみ公開
リリースフロー
changelog/{version}.mdを作成してリリースノートを書くnpm version {version}でバージョンバンプ+タグ作成git push && git push --tagsでプッシュ → GitHub Actions が自動で GitHub Release を作成npm publishで npm に手動公開
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.
- 8d ago First seen · 66 lines · 1,049 tokens per session scan A 948318ef9878
marp-mcp CLAUDE.md is an instructions file published in the GitHub repository masaki39/marp-mcp (11 stars, last pushed 3mo ago), licensed MIT. It adds 1,049 tokens to every session, about $0.0052 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.