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.
git clone --depth 1 https://github.com/specdog/dotdogWrote 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/rules/specdog/dotdog/cursorrules)<a href="https://agentmods.dev/rules/specdog/dotdog/cursorrules"><img src="https://agentmods.dev/badge/rules/specdog/dotdog/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/specdog/dotdog/cursorrules"><img src="https://agentmods.dev/badge/rules/specdog/dotdog/cursorrules.svg" alt="Reviewed on agentmods" width="80" 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.00427 | $0.00427 |
| Opus 5.5 | $0.00171 | $0.00171 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
cursorrules 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 1mo 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.
What it actually says
dotdog — spec-driven context for Cursor
Copy this file to your project root as .cursorrules
Cursor will auto-load dotdog MCP context on relevant tasks
Dotdog MCP Server
This project uses dotdog for structured specifications. Before any coding task that touches entities or relationships, query the dotdog MCP server to load relevant context.
Quick commands for your agent:
# Start the MCP server (if not running)
dotdog serve
# Or add to your Cursor MCP config (~/.cursor/mcp.json):
{
"mcpServers": {
"dotdog": {
"command": "npx",
"args": ["-y", "dotdog@latest", "serve"]
}
}
}
MCP tools available:
getEntity— Get entity properties, states, lifecycletraverse— Walk the graph from any node, BFS to depth Nsearch— Find entities by name or typeschema— Property definitions, zero prosesummary— Node count, edge count, token savingslistProjects— List all spec projects
Workflow:
dotdog doctor— verify specs are cleanlistProjects→ find your projectgetEntity→ understand an entity's properties and relationshipstraverse→ explore connected entities- Code with full context — no hallucinated APIs
When to query:
- Before creating/editing any file that touches spec entities
- Before suggesting API changes
- When you need to understand relationships between concepts
- When the user asks "how does X relate to Y?"
Spec files live in:
specs/<project>/SPEC.dog # product spec
specs/<project>/data-model.dog # entities, relationships, states
specs/<project>/constitution.dog # rules, constraints
specs/<project>/plan.dog # phases, tasks, predictions
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.
- 1mo ago First seen · 60 lines · 427 tokens per session scan A f6cfe75ff69b
cursorrules is a cursor rule published in the GitHub repository specdog/dotdog (7 stars, last pushed 2mo ago), licensed MIT. It adds 427 tokens to every session, about $0.0017 per session on Opus 5.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 cursor rules, from other repositories
release-checklist
What to update with each code change or version release.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.
05-daemons-ipc
Use this rule to understand the roles of the HAPPE/IDA/mcp-hostd daemons, how HAPPE and IDA communicate via IPC, find the IPC message structure definitions, trace the memory retrieval flow, and identify daemon responsibilities.
graphql
GraphQL: schema design, resolvers, performance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.