Borrowing it
Nothing to install: this file belongs to lacrif/mcp-archimate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lacrif/mcp-archimate/main/CLAUDE.mdgit clone --depth 1 https://github.com/lacrif/mcp-archimateWrote 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/lacrif/mcp-archimate/claude-md)<a href="https://agentmods.dev/instructions/lacrif/mcp-archimate/claude-md"><img src="https://agentmods.dev/badge/instructions/lacrif/mcp-archimate/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.01115 | $0.01115 |
| Opus 5 | $0.00558 | $0.00558 |
| Sonnet 5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
mcp-archimate 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Instructions
Task backlog and release notes
- The
TODO.mdfile centralizes all ongoing tasks for new releases. Before starting a task, review it: select an item or add one if necessary. - Once a task is complete, check the corresponding box in
TODO.md. - When a release is ready, move the checked items from
TODO.mdtoCHANGELOG.md. - Write concise and clear changelog entries (describe the changes, not the method). One bullet point per change.
- When tagging a release (e.g.
git tag 0.4.0), bumppackage.json"version"to match, runnpm test, commit the bump, then create the tag and push both:git push origin main --tags.
After every code change
- Run the tests:
npm test— all tests must pass before considering the change done. - Check coverage:
npm test -- --coverage— line/branch/function coverage must stay at or above 80%. If a change drops coverage below 80%, add tests before finishing. - Validate the .xml file: after any write/save operation, verify the file is valid by importing it with Archi:
A successfularchi -application com.archimatetool.commandline.app -consoleLog -nosplash --xmlexchange.import "data/archisurance.xml"[XML Exchange] Validated!+[XML Exchange] XML Imported!confirms the file is well-formed and conforms to the Open Exchange XSDs inmodels/. Cascade-deletes already strip dangling view nodes; identifiers generated by mutation handlers are prefixed withid-to satisfy thexs:ID/ NCName constraint. - Update the documentation: keep
README.mdin sync with any API, MCP tool, or behaviour change.
Image export conventions
- SVG/PNG exports: all view exports (SVG and PNG) go to
exports/views/. Never write generated images topublic/images/views/or any other directory. - Reference SVGs:
exports/references/contains SVGs exported directly by the Archi tool — these are the ground truth. When improving the renderer (src/renderer.ts), compare generated output against the matching file inexports/references/and minimize visual differences (shapes, colors, layout, connectors, labels, fonts).
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.
- 7d ago First seen · 57 lines · 1,115 tokens per session scan A 9af1bf8373db
mcp-archimate CLAUDE.md is an instructions file published in the GitHub repository lacrif/mcp-archimate (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,115 tokens to every session, about $0.0056 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.