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/dogganidhal/noddde/claude-mdgit clone --depth 1 https://github.com/dogganidhal/nodddeWrote 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/dogganidhal/noddde/claude-md)<a href="https://agentmods.dev/instructions/dogganidhal/noddde/claude-md"><img src="https://agentmods.dev/badge/instructions/dogganidhal/noddde/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.01890 | $0.01890 |
| Opus 5 | $0.00945 | $0.00945 |
| Sonnet 5 | $0.00378 | $0.00378 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
noddde 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
noddde — Claude Development Guide
Project Overview
noddde is a TypeScript framework for DDD, CQRS, and Event Sourcing using the functional Decider pattern: no base classes, no decorators — just typed objects and pure functions.
Current state: API surface complete, in-memory runtime implemented, 5 sample domains as references. See docs/ARCHITECTURE.md for design philosophy, anti-goals, and competitive context.
Spec Authority Principle
Specs are the source of truth. Spec wins for behavioral requirements — fix the code, not the spec. Code wins for type-level details TypeScript enforces — update the spec. Spec-first: always write or update the spec before changing code.
Monorepo Layout (Turborepo + Yarn)
packages/core/— Types, interfaces, definition functions (@noddde/core) — zero runtime depspackages/engine/— Runtime: Domain orchestration + in-memory implementations (@noddde/engine)packages/cli/— CLI tool for scaffolding aggregates, projections, sagas (@noddde/cli)packages/samples/— 3 reference domains (auction, banking, order-fulfillment)docs/— Fumadocs documentation sitespecs/— Behavioral specs (mirror source directories). Seespecs/README.md
Architecture
Core (packages/core/src/): ddd/ (aggregate, projection, saga), edd/ (event, event-bus, handlers), cqrs/ (command/query buses + handlers), infrastructure/, persistence/. See index.ts for exports.
Engine (packages/engine/src/): domain.ts (orchestrator), implementations/ (in-memory backends for all buses, persistence, snapshots, locking).
Key patterns: *Types bundles (named type containing state/events/commands/infrastructure), Define* mapped type builders, define* identity functions for inference, Decider pattern (initialState + decide + evolve), infrastructure as function parameters.
Spec System
Specs live in specs/ mirroring source: packages/core/src/<path>.ts → specs/core/<path>.spec.md.
Sections: Type Contract, Behavioral Requirements (numbered), Invariants, Edge Cases, Integration Points, Test Scenarios (vitest code blocks). See specs/README.md for full format documentation.
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.
- 6d ago First seen · 126 lines · 1,890 tokens per session scan A c6297440cede
noddde CLAUDE.md is an instructions file published in the GitHub repository dogganidhal/noddde (48 stars, last pushed 6d ago), licensed MIT. It adds 1,890 tokens to every session, about $0.0095 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
event-store-adapter-js AGENTS.md
AGENTS.md instructions for j5ik2o/event-store-adapter-js, covering agents.md, 言語, github pull request のモニタリング, $grill-me 実行時の作業判断 and 軽い作業の場合.
event-store-adapter-js CLAUDE.md
Claude Code instructions for j5ik2o/event-store-adapter-js, a project described as: This library is designed to turn DynamoDB into an Event Store for Event Sourcing.
event-store-adapter-js GEMINI.md
Gemini CLI instructions for j5ik2o/event-store-adapter-js, a project described as: This library is designed to turn DynamoDB into an Event Store for Event Sourcing.
fastify-boilerplate AGENTS.md
AGENTS.md instructions for marcoturi/fastify-boilerplate, covering agents.md, project overview, quick reference, architecture and layer boundaries (critical).
duragraph go.instructions.md
Instructions for Duragraph/duragraph, covering go code review instructions, project overview, strict layer rules, domain aggregate pattern and run state machine.
adl AGENTS.md
AGENTS.md instructions for inference-gateway/adl, covering agents.md, commands, schema versioning contract — the most important rule, style and testing.