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/andrewhopper/dotai/claude-mdgit clone --depth 1 https://github.com/andrewhopper/dotaiWrote 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/andrewhopper/dotai/claude-md)<a href="https://agentmods.dev/instructions/andrewhopper/dotai/claude-md"><img src="https://agentmods.dev/badge/instructions/andrewhopper/dotai/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.00814 | $0.00814 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
dotai 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - AI Assistant Guide for Dot AI
ID Naming Convention
Each file and section will follow this ID structure:
- Files:
{folder-prefix}-{file-name}-{sequence}(e.g.,CTX-project-conventions-001) - Sections:
{file-id}:{section-type}-{sequence}(e.g.,CTX-project-conventions-001:REQ-001)
Folder Prefixes
CFG: 0-ai-configCTX: 1-contextARCH: 2-technical-designDEV: 3-development (implementation tasks)PRD: 3-development (product requirements)QA: 4-acceptence-reports
Section Types
REQ: RequirementSPEC: SpecificationIMPL: ImplementationTEST: TestVAL: ValidationFEAT: FeatureBUG: Bug fixCHORE: Maintenance taskTASK: General taskSTORY: User storyEPIC: Collection of related storiesSPIKE: Research or exploration task
Example Usage
A feature requirement might be referenced as:
ARCH-auth-feature-001:REQ-003 (PASS)
This references:
- File:
/2-technical-design/features/auth-feature.md(ID: ARCH-auth-feature-001) - Section: Requirement #3 in that file (ID: REQ-003)
- Status: PASS
Implementation Guidelines
- Add ID frontmatter to each file:
--- id: ARCH-auth-feature-001 created: 2025-03-15 --- - Add section IDs as HTML comments or in headings:
## Authentication Flow <!-- REQ-003 --> - Reference IDs in validation reports:
| Requirement ID | Status | Notes | |---------------|--------|-------| | ARCH-auth-feature-001:REQ-003 | PASS | All tests passing | | PRD-login-feature-002:STORY-001 | PASS | Verified by QA |
ID Usage Examples
PRD-login-feature-001:STORY-002: Product requirement for login feature, story #2DEV-authentication-001:IMPL-005: Development implementation for authentication, implementation detail #5QA-security-report-001:TEST-003: QA security test report, test case #3
Project Commands
- Install:
npm install(future) - Build:
npm run build(future) - Lint:
npm run lint(future) - Test:
npm test(future) - Test single file:
npm test -- -f path/to/test(future)
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 · 93 lines · 814 tokens per session scan A c2a71b0598b1
dotai CLAUDE.md is an instructions file published in the GitHub repository andrewhopper/dotai (56 stars, last pushed 9mo ago), licensed MIT. It adds 814 tokens to every session, about $0.0041 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
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).
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.
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.
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).
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.