agentmods.dev

dotdog CLAUDE.md

A set of instructions for Dotdog, a project that represents software entities and relationships in compiled graph files. It requires agents to use the smaller .dag file as the source of truth instead of reading the original .dog files directly.

In plain words
What is it for?
Use it when inspecting Dotdog entities and relationships, querying project structure, changing code against the graph, and running validation before committing.
Why use it?
It prevents agents from guessing the project's structure or using stale source data. Validation checks whether changes preserve the graph's quality.

Instructions file

5 +1 1mo ago A scan 450 tokens original MIT
View the source file specdog/dotdog
Install

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.

agentmods
npx agentmods add instructions/specdog/dotdog/claude-md
Clone the repo
git clone --depth 1 https://github.com/specdog/dotdog
Per session 450 This file is loaded in full into every session.
When invoked 450 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00450 $0.00450
Opus 5 $0.00225 $0.00225
Sonnet 5 $0.00090 $0.00090
Haiku 4.5 $0.00045 $0.00045

Measured 2d ago against content hash bf7af4476100, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dotdog 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 2d 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.

CLAUDE.md · 39 lines

What it actually says

CLAUDE.md — dotdog

You are an AI agent working on a dotdog project. This file is your ground truth.

Before you do anything

  1. NEVER read .dog files directly. The .dag is the compiled source of truth. Reading .dog is reading the compiler input — not your layer.

Read .md files for context (README, docs, blog) but NEVER use .md for entity names, relationships, or project structure. Only .dag has that.

  1. Find the .dag file: find . -name "*.dag" -not -path "*/node_modules/*"
  2. Load it. This is 94% smaller than the .dog source files. It has the full entity graph.
  3. If MCP is available, run npx dotdog serve for live queries.

Key rules

  • Load the .dag before reading any code file. If you read .dog or .md without the .dag, you are guessing. Use MCP tools to query the .dag — never scan .dog files directly.
  • Do not grep for structure. The .dag has entity names, properties, relationships. Use it.
  • If code contradicts .dag, .dag wins. Fix code toward .dag. Never fix .dag toward code.
  • Run dotdog validate before committing. Score must not decrease.
  • If the .dag says nothing about something, say "unverified." Do not speculate.

Commands

Command When
dotdog validate Before committing spec changes
dotdog compile After editing .dog files
dotdog staleness Check spec/reality drift
dotdog serve Start MCP for live queries

MCP tools

When dotdog serve is running: getEntity, traverse, search, schema, summary, listProjects.

More

Changes

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.

  1. 2d ago First seen · 39 lines · 450 tokens per session scan A bf7af4476100

Subscribe to this mod's changes

dotdog CLAUDE.md is an instructions file published in the GitHub repository specdog/dotdog (5 stars, last pushed 1mo ago), licensed MIT. It adds 450 tokens to every session, about $0.0022 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.

aiclidogfooddotdogspecspecification
Related

Other instructions, from other repositories

agents

Startup protocol — safe for all collaborators. MCP section is conditional.

xy200303/spec-coding-mcp · 819 tokens

claude

Startup protocol for Claude-style agents — safe for all collaborators.

xy200303/spec-coding-mcp · 821 tokens

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.

github/spec-kit · 7,104 tokens

agent-spec AGENTS.md

Instructions for ZhangHanDong/agent-spec, covering agent-spec integration for codex / openai agents, part 1: tool-first workflow, core mental model, quick reference and rust atlas workflow.

ZhangHanDong/agent-spec · 7,092 tokens

agent-plugins-spec AGENTS.md

AGENTS.md instructions for agentplugins/agent-plugins-spec, covering agent instructions, purpose and authority, design posture, portability boundaries and editorial discipline.

agentplugins/agent-plugins-spec · 868 tokens

leanspec AGENTS.md

Instructions for codervisor/leanspec, covering ai agent instructions, project: leanspec, skills, spec-driven development (github-issue specs) and development & tooling.

codervisor/leanspec · 984 tokens