docs CLAUDE.md

Project instructions for the Miden documentation website, built with Docusaurus, a tool for publishing documentation sites. They describe its directories, commands, technology choices, and rules for links and builds.

In plain words
What is it for?
Use them when editing Miden docs, builder guides, reference pages, React components, styles, or release assets. They also specify the checks to run before proposing changes.
Why use it?
They help an agent make changes that fit the repository and catch broken documentation before a pull request. The instructions also identify where current and versioned documentation live.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/0xmiden/docs/claude-md
Clone the repo
git clone --depth 1 https://github.com/0xMiden/docs
Per session 559 This file is loaded in full into every session.
When invoked 559 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00559 $0.00559
Opus 5 $0.00280 $0.00280
Sonnet 5 $0.00112 $0.00112
Haiku 4.5 $0.00056 $0.00056

Measured 2d ago against content hash 1716d0422839, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs CLAUDE.md scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Always verify URLs** — `curl -sL -o /dev/null -w "%{http_code}" <url>` before adding/changing links
CLAUDE.md · 48 lines

How it starts

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

Miden Docs — CLAUDE.md

Project

Docusaurus v3 documentation site for the Miden ecosystem. Deployed at docs.miden.xyz.

Key Directories

  • docs/ — current docs (reference, builder/)
  • docs/builder/ — developer-facing: tools, develop, get-started, smart-contracts, migration
  • docs/reference/ — protocol design docs
  • versioned_docs/ — pinned version snapshots
  • src/ — custom React components, pages, CSS
  • static/ — images, assets
  • .release/release-manifest.yml — version info (read by docusaurus.config.ts)

Commands

npm run build          # Full production build — ALWAYS run before PRing
npm run start          # Dev server with hot reload
npm run typecheck      # TypeScript check
npm run clear          # Clear Docusaurus cache (if builds are stale)
npm run generate:og    # Regenerate static Open Graph images

Rules

  • Always npm run build before creating PRs — catches broken links and build errors
  • Always verify URLscurl -sL -o /dev/null -w "%{http_code}" <url> before adding/changing links
  • Broken links: onBrokenLinks: "warn" in config — treat warnings as errors for PRs
  • Math: uses remark-math + rehype-katex for LaTeX
  • Algolia search is configured

Conventions

  • Conventional commits: docs:, fix:, feat:
  • Batch related small fixes into single PRs
  • PR titles should be descriptive, not just "update docs"
  • Keep markdown clean: no trailing whitespace, consistent heading levels
  • Internal links: use relative paths, not absolute URLs
  • Images go in static/img/ with descriptive names
  • Open Graph cards: when adding or moving a top-level docs section, update src/utils/ogImages.ts and scripts/generate-og-images.mjs. npm run build runs npm run generate:og first, so include any generated static/img/og/*.png changes in the PR.

Gotchas

  • versioned_docs/ and versioned_sidebars/ are auto-generated — don't edit manually unless you need to update the versioned_docs release contents
  • sidebars.ts controls navigation — update when adding/removing pages
  • Release manifest YAML drives version display — don't edit unless releasing
  • Some custom components in src/ — check before adding new ones

Read the full file on GitHub · 48 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.

  1. 2d ago First seen · 48 lines · 559 tokens per session scan A 1716d0422839

Subscribe to this mod's changes

docs CLAUDE.md is an instructions file published in the GitHub repository 0xMiden/docs (9 stars, last pushed 5d ago), licensed MIT. It adds 559 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens