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/khan/wonder-blocks/claude-mdgit clone --depth 1 https://github.com/Khan/wonder-blocksWrote 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/khan/wonder-blocks/claude-md)<a href="https://agentmods.dev/instructions/khan/wonder-blocks/claude-md"><img src="https://agentmods.dev/badge/instructions/khan/wonder-blocks/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.03823 | $0.03823 |
| Opus 5 | $0.01912 | $0.01912 |
| Sonnet 5 | $0.00765 | $0.00765 |
| Haiku 4.5 | $0.00382 | $0.00382 |
Grade A, and why
wonder-blocks 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 5d 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wonder Blocks Design System
This file provides instructions for Claude when working on the Wonder Blocks design system codebase.
Technology Stack
- Language: TypeScript (Strict mode enforced)
- Framework: React (Functional Components and Hooks)
- Styling: Aphrodite (
aphrodite) for CSS-in-JS with Wonder Blocks tokens (@khanacademy/wonder-blocks-tokens) - State Management: Local state (
useState) and React Context API (useContext) - Data Fetching: There should be no data fetching in the design system UI components
- Routing: Design system components with link functionality should also support React-Router routes
- Testing: Jest, React Testing Library (RTL),
@testing-library/user-event, Storybook - Package Manager: pnpm
Coding Conventions
File & Export Naming
- Use kebab-case for files and directories (e.g.,
activity-button.tsx,utils.ts) - Test files:
*.test.ts(x) - Storybook files:
*.stories.tsx - PascalCase for React components and types (e.g.,
Button,type ButtonProps) - camelCase for functions, variables, hooks (e.g.,
getButtonProps,useButtonFunctionality)
TypeScript
- Use
strictmode - Define clear interfaces/types. Use
typefor props and state,interfacefor shared structures where appropriate - Use utility types (
Partial,Omit,Pick,Readonly, etc.) - Use the
satisfiesoperator for type-safe object literals - Prefer type-only imports:
import type {...}for types - Avoid
any; useunknownor specific types instead
React
- Imports: Always use
import * as React from "react"(required for JSX transformation) - Use functional components and hooks (
useState,useEffect,useContext,useCallback,useMemo) - Define explicit
Propstypes with object destructuring. Pass complex objects/callbacks with stable references (useCallback,useMemo) if they are dependencies of effects or memoized children - Keep component state minimal. Lift state up when necessary
- Provide stable
keyprops for lists (use item IDs if available) - Build complex UI by composing smaller Wonder Blocks when possible
- Use
React.forwardRefwhen components need to expose DOM refs - Extract reusable logic into custom hooks (e.g.,
useFieldValidation,useIsMountedfrom@khanacademy/wonder-blocks-core) - Event Handlers: Internal handlers prefixed with
handle(e.g.,handleClick), callback props prefixed withon(e.g.,onClick) - Don't use
React.FC<Props>, use(props: Props) =>instead - Avoid creating new class components
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.
- 5d ago First seen · 316 lines · 3,823 tokens per session scan A e70379b60e56
wonder-blocks CLAUDE.md is an instructions file published in the GitHub repository Khan/wonder-blocks (163 stars, last pushed today), licensed MIT. It adds 3,823 tokens to every session, about $0.0191 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
balsa-ui AGENTS.md
Instructions for pedrobalsa/balsa-ui, a project described as: Agent-native, open-code Vue/React components with independent palettes, themes, and gradient backgrounds.
material-ui CLAUDE.md
Claude Code instructions for mui/material-ui: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
thunderbolt AGENTS.md
AGENTS.md instructions for thunderbird/thunderbolt, covering core principles, typescript & code style, tooling & libraries, react patterns and useeffect discipline.
ark CLAUDE.md
Claude Code instructions for chakra-ui/ark, covering ark ui - claude development guide, documentation structure, quick start, common commands and install dependencies.
ui-components AGENTS.md
AGENTS.md instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
webcomponents-react CLAUDE.md
Claude Code instructions for UI5/webcomponents-react, covering claude.md, critical: working with web components, event handling (must know), controlled components (must know) and ref handling (must know).