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/zjyao36/markdown-claude-code/claude-mdgit clone --depth 1 https://github.com/zjYao36/markdown-claude-codeWrote 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/zjyao36/markdown-claude-code/claude-md)<a href="https://agentmods.dev/instructions/zjyao36/markdown-claude-code/claude-md"><img src="https://agentmods.dev/badge/instructions/zjyao36/markdown-claude-code/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 | $0.00970 | $0.00970 |
| Opus 5 | $0.00485 | $0.00485 |
| Sonnet 5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
markdown-claude-code 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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with code in this repository.
What This Is
A Claude Code skill (/writing-cc) that produces high-quality, research-backed written documents through an automated pipeline: requirements analysis → rubric derivation → research + drafting → iterative GPT review and revision (4-5 rounds). The core logic lives entirely in writing-cc/SKILL.md.
Installation
# Install skill
cp -r writing-cc ~/.claude/skills/
# Set up Codex MCP for external reviewer (GPT-4o)
npm install -g @openai/codex
claude mcp add codex -s user -- codex mcp-server
Place local reference materials (papers, notes) in papers/ and literature/ for grounding during research.
Usage
/writing-cc "document request"
Example:
/writing-cc 我现在需要总结一下计算机视觉、机器学习顶会论文Introduction的写作秘诀，请你参考近几年CVPR、NeurIPS、ICLR的Best Paper，以及Kaiming He的过往优秀论文，细致总结出来好的Introduction应该怎么写,有些失效链接打不开就不用强行打开，最终目的是总结规律，不要为了找论文而浪费时间
Architecture
6-phase iterative pipeline (max 5 review rounds, exits early if overall score >= 8.5):
- Phase 0 — Analyze requirements: extract goal, audience, key topics, sources, constraints →
writing-logs/phase0-requirements.md - Phase 1 — Derive evaluation rubric: 5-7 measurable criteria tailored to the specific document request →
writing-logs/phase1-rubric.md - Phase 2 — Research (web search + local files) + write first draft →
writing-logs/round-0-draft.md - Phase 3 — Send rubric + draft to GPT-4o via Codex MCP (
mcp__codex__codex) for structured scoring and feedback; savethreadId - Phase 4 — Parse review, apply revisions, Goal Check before each round →
writing-logs/round-N-revision.md - Phase 5 — Re-evaluate via same Codex thread (
mcp__codex__codex-reply) →writing-logs/round-N-review.md - Phase 6 — Generate clean
FINAL_DOCUMENT.mdand fullWRITING_REPORT.md
Key config: REVIEWER_MODEL = gpt-4o, MAX_ROUNDS = 5, SCORE_THRESHOLD = 8.5.
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 · 77 lines · 970 tokens per session scan A 8c9f637c3d5f
markdown-claude-code CLAUDE.md is an instructions file published in the GitHub repository zjYao36/markdown-claude-code (5 stars, last pushed 5mo ago), licensed MIT. It adds 970 tokens to every session, about $0.0049 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.