Borrowing it
Nothing to install: this file belongs to MAIAS-project/maias. 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/MAIAS-project/maias/main/CLAUDE.mdgit clone --depth 1 https://github.com/MAIAS-project/maiasWrote 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/maias-project/maias/claude-md)<a href="https://agentmods.dev/instructions/maias-project/maias/claude-md"><img src="https://agentmods.dev/badge/instructions/maias-project/maias/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.01509 | $0.01509 |
| Opus 5 | $0.00754 | $0.00754 |
| Sonnet 5 | $0.00302 | $0.00302 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
maias 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Conventions
This repo is MAIAS (Mobile App Information Architecture Schema): an open standard plus tooling, generalised from an earlier working prototype. The authoritative definition of MAIAS documents is the spec at docs/spec/ (condensed agent reference: docs/spec/llms.txt) and schema/maias.schema.json — the IA Schema section below is a convenience summary and defers to the spec wherever they disagree.
Terminology
- "IA" refers to the MAIAS document being worked on — one of the
examples/*/maias.yamldocuments or a user-supplied file (spec 0.3 shape: amaias:version header,elements:lists, neutral element type names — seedocs/spec/05-elements.md) - "Primary" refers to the primary navigation elements present at the 'root' of the app IA
- "Secondary" refers to the secondary navigation elements, usually these change depending upon context and lead to other screens in the app
- "Actions" refer to interactive elements which don't lead anywhere
Changes
- Any changes must be made to the IA first, and then rendered automatically in the app and quick nav
- If I ask for any changes to be made the IA items, such as renaming, always ensure that the corresponding paths and references in the flows and navigation are also updated
- Validate IA changes with
./node_modules/.bin/maias validate <file>and format withmaias fmt <file> --write(built frompackages/cli) - Quality gate before any commit:
npm run typecheck(workspaces) +npx vitest runat the repo root +npx tsc --noEmitinMAIAS_browser/
IA Schema
Navigation
Top-level navigation defines which screens are accessible globally.
navigation:
primary:
label: <string> # Display label for the nav group
screens: # Screens shown in the persistent tab bar
- <screen_id>
secondary:
label: <string>
screens: # All non-primary screens in the app
- <screen_id>
- Primary screens appear in the tab bar and are always accessible
- Secondary screens are all other screens, listed here as a registry
- Every screen in the app must appear in either
primary.screensorsecondary.screens
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 · 129 lines · 1,509 tokens per session scan A d18de0dfa312
maias CLAUDE.md is an instructions file published in the GitHub repository MAIAS-project/maias (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,509 tokens to every session, about $0.0075 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
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).
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.
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.
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).
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.