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/dafthunk-com/dafthunkWrote 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/dafthunk-com/dafthunk/03-project-structure)<a href="https://agentmods.dev/rules/dafthunk-com/dafthunk/03-project-structure"><img src="https://agentmods.dev/badge/rules/dafthunk-com/dafthunk/03-project-structure/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/dafthunk-com/dafthunk/03-project-structure"><img src="https://agentmods.dev/badge/rules/dafthunk-com/dafthunk/03-project-structure.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.00162 | $0.00162 |
| Opus 5.5 | $0.00065 | $0.00065 |
| Sonnet 5.5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
03-project-structure 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
Project Structure
The repository is organized in a monorepo using pnpm workspaces: pnpm-workspace.yaml. It contains the following:
- apps/api: package.json
- apps/web: package.json
- pacakges/types: package.json
With the root package.json being: package.json
- When executing command in specific workspaces, use the
--filter @dafthunk/webfor example in order to execute a pnpm command in the web workspace.
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 · 16 lines · 162 tokens per session scan A 43196d46f211
03-project-structure is a cursor rule published in the GitHub repository dafthunk-com/dafthunk (137 stars, last pushed 1mo ago), licensed MIT. It adds 162 tokens to every session, about $0.0006 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-30.
Other cursor rules, from other repositories
cpp
Name methods (casing, etc) like "isvalid", "streamtext".
ai_docs
There is a folder called aidocs it contains useful resources for reference.
run-scripts
when running any thing in scripts dir do "uv run ".
turborepo
Turbo task-graph rationale, query graph primitives, and signed remote-cache key provisioning.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
on-load-rule
This guide outlines the critical development principles for this Swift project.