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/caspii/dinkydash/claude-mdgit clone --depth 1 https://github.com/caspii/dinkydashWrote 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/caspii/dinkydash/claude-md)<a href="https://agentmods.dev/instructions/caspii/dinkydash/claude-md"><img src="https://agentmods.dev/badge/instructions/caspii/dinkydash/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.02199 | $0.02199 |
| Opus 5 | $0.01099 | $0.01099 |
| Sonnet 5 | $0.00440 | $0.00440 |
| Haiku 4.5 | $0.00220 | $0.00220 |
Grade A, and why
dinkydash 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 today.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today Changed · +60 lines · +798 tokens per session a892a7d2e6ae
- 6d ago First seen · 130 lines · 1,401 tokens per session scan A b159cf828e39
dinkydash CLAUDE.md is an instructions file published in the GitHub repository caspii/dinkydash (93 stars, last pushed yesterday), with no licence file. It adds 2,199 tokens to every session, about $0.0110 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
Ignite AGENTS.md
AGENTS.md instructions for Sumukh/Ignite, covering agents.md, what this repo is, fast start (local development), seed local sqlite db with starter users and run app.
Gladys AGENTS.md
AGENTS.md instructions for GladysAssistant/Gladys, covering agents.md, cursor cloud specific instructions, running the app (dev mode), non-obvious caveats and feature specs (spec-first process).
core copilot-instructions.md
Copilot instructions for home-assistant/core, covering copilot code review instructions, pull request template, breaking change, proposed change and type of change.
autonomous-os AGENTS.md
AGENTS.md instructions for autonomous-ai/autonomous-os, covering agents.md, multi-ide rules, working style, parallel work / subagents and device access rules.
raspibolt CLAUDE.md
Claude Code instructions for raspibolt/raspibolt, covering raspibolt: development guidelines, working rules, autonomy model, level 0: autonomous and level 1: inform.
build123d-mcp CLAUDE.md
Claude Code instructions for pzfreo/build123d-mcp, covering build123d-mcp, running tests, running the server, project structure and adding a new tool.