Borrowing it
Nothing to install: this file belongs to kzmshx/frontmatter-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/kzmshx/frontmatter-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/kzmshx/frontmatter-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/kzmshx/frontmatter-mcp/claude-md)<a href="https://agentmods.dev/instructions/kzmshx/frontmatter-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kzmshx/frontmatter-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.00466 | $0.00466 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
frontmatter-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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Conventional Commits / Branch Naming
| type | purpose |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Changes that don't affect code meaning (whitespace, formatting) |
refactor |
Code change that is neither a fix nor a feature |
test |
Adding or modifying tests |
chore |
Build process or tooling changes |
Branch name: {type}/{description} (e.g., feat/rename-tools, fix/json-encoding)
PR Review Handling
| Operation | Command |
|---|---|
| Check CI | gh pr checks {n} |
| Get comments | gh api repos/{owner}/{repo}/pulls/{n}/comments |
| Reply | gh api repos/{owner}/{repo}/pulls/{n}/comments/{comment_id}/replies -X POST -f body="..." |
Reply to comments with commit hash after fixes.
Documentation Structure
docs/adr/
Managed with adr CLI (adr-tools). Git tracked.
- Create:
adr new <title> - List:
adr list - Supersede:
adr new -s <number> <title>
Documentation Rules
Common Rules
- No emojis
- No horizontal rules (
---)
Common Style
- State facts concisely
- Avoid unnecessary decoration or verbose explanations (lists and tables are fine for readability)
- Show concrete examples for code and config
Security Rules (Important)
Documents under docs/ are Git tracked, so the following are prohibited:
- Private keys, tokens, passwords
- API keys, credentials
- Personally identifiable information (names, emails, usernames)
- Local environment paths (e.g.,
/Users/username/) - Project IDs and resource names are OK (e.g.,
exp-batch-predictions) - For specific config values, reference template files like
.env.example - Local environment info should go in
CLAUDE.local.md
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 · 61 lines · 466 tokens per session scan A 08b87aa6e689
frontmatter-mcp CLAUDE.md is an instructions file published in the GitHub repository kzmshx/frontmatter-mcp (1 stars, last pushed 8mo ago), licensed MIT. It adds 466 tokens to every session, about $0.0023 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
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.