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/akonan/wiremd/claude-mdgit clone --depth 1 https://github.com/akonan/wiremdWrote 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/akonan/wiremd/claude-md)<a href="https://agentmods.dev/instructions/akonan/wiremd/claude-md"><img src="https://agentmods.dev/badge/instructions/akonan/wiremd/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.01024 | $0.01024 |
| Opus 5 | $0.00512 | $0.00512 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
wiremd 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 — 75 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 (claude.ai/code) when working with code in this repository.
What this is
wiremd converts Markdown with extended wireframing syntax into visual wireframes. It ships as an npm library, a CLI tool, and a VS Code extension. Input is .md files with wiremd syntax; output is HTML (7 styles), React/JSX, Tailwind, or JSON.
Commands
npm run build # TypeScript + Vite → dist/
npm test # Run all tests (vitest)
npm test -- tests/parser.test.ts # Single test file
npm test -- tests/parser.test.ts -t "Button" # Single test by name
npm run test:coverage
npm run typecheck # Strict TypeScript check
npm run lint # ESLint on src/
npm run docs:dev # VitePress docs dev server
CLI usage (after build):
wiremd input.md --style clean --serve 3001 --watch
wiremd input.md -o output.html -f html -s sketch
Architecture
The pipeline: Markdown string → parse() → WiremdAST → render*() → HTML/React/JSON/Tailwind
src/
├── types.ts # ~40 discriminated-union AST node types
├── index.ts # Public exports
├── parser/
│ ├── index.ts # parse() + validate(); calls resolveIncludes()
│ ├── transformer.ts # MDAST → wiremd AST (the bulk of parsing logic)
│ ├── remark-containers.ts # ::: block syntax plugin (supports nesting)
│ └── remark-inline-containers.ts # [[ ... ]] nav/inline syntax plugin
└── renderer/
├── index.ts # renderToHTML(), renderToReact(), renderToJSON(), renderToTailwind()
├── html-renderer.ts # Component → HTML string (handles all node types)
├── react-renderer.ts # Component → React/JSX string
├── tailwind-renderer.ts # Component → Tailwind-classed HTML
└── styles.ts # 7 CSS style systems (sketch, clean, wireframe, material, brutal, tailwind, none)
Parser flow: unified/remark parses standard Markdown into MDAST, then remark-containers and remark-inline-containers handle wiremd-specific syntax (::: card, [[ nav ]], buttons [Label]*, inputs [_____]). The transformer walks the MDAST and emits wiremd AST nodes.
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 · 75 lines · 1,024 tokens per session scan A bad1b62962fc
wiremd CLAUDE.md is an instructions file published in the GitHub repository akonan/wiremd (97 stars, last pushed 3mo ago), licensed MIT. It adds 1,024 tokens to every session, about $0.0051 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
mq commit.instructions.md
Instructions for harehare/mq: Use the following format for commit messages.
core copilot-instructions.md
Instructions for asdecided/core: These decisions are already accepted. Do not re-open or contradict them; ask the AsDecided MCP tools (getartifact, searchartifacts) for the full text before proposing a change that touches one.
telegramify-markdown AGENTS.md
Instructions for sudoskys/telegramify-markdown, covering telegramify-markdown agent guide, task routing, quick commands, project rules and architecture map.
easy-notion-mcp CLAUDE.md
Instructions for Grey-Iris/easy-notion-mcp, covering easy-notion-mcp, open source context, .meta/ publication policy (hybrid, 2026-07-02), standing priorities and commands.
research-os AGENTS.md
Instructions for lxinfei5/research-os, covering researchos — constitution, §0 what this is, §1 directory discipline, §2 half-life (innovation 1) — memory design and §3 behavior pillars (innovations 2–5).
markview CLAUDE.md
Instructions for paulhkang94/markview, covering markview — ai development guide, quick reference, architecture, mcp tools (for ai integration) and safety rules.