What is md2do CLAUDE.md?

Repository instructions for md2do, a project split into multiple related packages in one repository, known as a monorepo. They describe its build, test, lint, type-check, and npm release process.

Use them when developing or releasing md2do packages such as core, CLI, Todoist, MCP, VS Code, and Obsidian integrations.

They give an agent the project’s required commands and release rules, including how package changes are versioned and published. This helps avoid incorrect manual releases.

How TeamNickHart/md2do configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to TeamNickHart/md2do. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/TeamNickHart/md2do/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/TeamNickHart/md2do

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/teamnickhart/md2do/claude-md/github.svg)](https://agentmods.dev/instructions/teamnickhart/md2do/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/teamnickhart/md2do/claude-md"><img src="https://agentmods.dev/badge/instructions/teamnickhart/md2do/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/teamnickhart/md2do/claude-md"><img src="https://agentmods.dev/badge/instructions/teamnickhart/md2do/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,012 This file is loaded in full into every session.

When invoked 1,012 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01012	$0.01012
Opus 5.5	$0.00405	$0.00405
Sonnet 5.5	$0.00202	$0.00202
Haiku 4.5	$0.00101	$0.00101

Measured 28d ago against content hash a10c7884e584, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

md2do 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 28d 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.

CLAUDE.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

md2do — Claude Instructions

Repository

pnpm monorepo. Packages: core, cli, config, todoist, mcp, vscode, obsidian.

pnpm build          # build all packages
pnpm -r run test:run  # run all tests
pnpm lint           # lint all packages
pnpm typecheck      # typecheck all packages

Release Process

The only correct release flow is via publish.yml + changesets. Do not create GitHub Releases manually.

Steps

Include a changeset in every feature PR that changes published packages:

pnpm changeset
# select affected packages, choose bump type, write summary
# commit the generated .changeset/*.md file with the PR

Merge the feature PR to main. Nothing is published yet.
Open the version PR by hand when ready to release:
```
git switch -c chore/version-vX.Y.Z main
GITHUB_TOKEN=$(gh auth token) pnpm run version  # changeset version + lockfile
```
GITHUB_TOKEN is needed by the GitHub changelog generator. Commit the result and open a PR titled "chore: version packages to vX.Y.Z".

changeset version also bumps the private dependents md2do-vscode and md2do-obsidian. Keep the md2do-vscode bump only if the extension actually changed (and add a real CHANGELOG line); revert the md2do-obsidian bump unless the plugin changed.
Merge the version PR. publish.yml detects no changeset files remain and runs:
```
pnpm release  # = pnpm build && changeset publish --provenance
```
Packages are published to npm via OIDC Trusted Publishing — no token required.

What NOT to do

Do not create GitHub Releases to trigger publishing — release.yml has been deleted.
Do not use NPM_TOKEN — Trusted Publishing is configured on npmjs.com for all @md2do/* packages.
Do not run changeset publish locally unless debugging — the merge of the version PR publishes.
Do not expect publish.yml to open the version PR. It can't: the repo doesn't allow GitHub Actions to create pull requests, and a PR opened by the Actions token wouldn't trigger the required CI Success check anyway. Until that is set up, the Publish run on a feature merge fails at "creating pull request"; that failure is expected and harmless.
Do not bump versions in package.json manually — changesets manages this.

Read the full file on GitHub · 104 lines

Changes

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.

28d ago Changed · +17 lines · +225 tokens per session a10c7884e584
2mo ago First seen · 87 lines · 787 tokens per session scan A 42e004d1dae3

Subscribe to this mod's changes

md2do CLAUDE.md is an instructions file published in the GitHub repository TeamNickHart/md2do (3 stars, last pushed 28d ago), licensed MIT. It adds 1,012 tokens to every session, about $0.0040 per session on Opus 5.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.

claude cli markdown mcp mcp-server md

md2do CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
md2do CLAUDE.mdTeamNickHart/md2do	Instructions file	3	28d ago	MIT	A	1,012	Claude Code
md-feedback copilot-instructions.mdyeominux/md-feedback	Instructions file	5	7mo ago	none	A	309	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot

md2do: Instructions file for Claude Code