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/jamiedavenport/capd/claude-mdgit clone --depth 1 https://github.com/jamiedavenport/capdWrote 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/jamiedavenport/capd/claude-md)<a href="https://agentmods.dev/instructions/jamiedavenport/capd/claude-md"><img src="https://agentmods.dev/badge/instructions/jamiedavenport/capd/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 | $0.00264 | $0.00264 |
| Opus 5 | $0.00132 | $0.00132 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
capd 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 5d 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
Capd
Open-source native macOS capture/bookmarking app — the Pinboard successor.
Linear
- Use Linear's branch names so that PRs are automatically linked.
Comments
- Comments are a cost. Default to none.
- Write one only to explain why — a workaround, constraint, or deliberate trade-off the code can't convey.
- Or as a
///doc comment on public API. - If a comment is needed to make code understandable, rename or restructure first.
- Never restate what the code does, narrate what a file will contain later, or justify an import or dependency.
External state
- Never reference Linear IDs, ticket codes, or decision labels (
A5,T9,X1) in source, config, or docs. - Never add
TODO(TICKET), "coming in v0.2", or "Status: scaffold". - These go stale silently and can't be verified from the codebase.
- Rationale belongs in commit messages and PR descriptions.
- Roadmap belongs in Linear or Github issues.
- Architecture belongs in
docs/designs/.
READMEs
- Describe what exists, in the present tense.
- If a section can only be written in the future tense, leave it out.
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.
- 5d ago First seen · 30 lines · 264 tokens per session scan A 940a02a554af
capd CLAUDE.md is an instructions file published in the GitHub repository jamiedavenport/capd (43 stars, last pushed 21d ago), licensed MIT. It adds 264 tokens to every session, about $0.0013 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
cctop AGENTS.md
AGENTS.md instructions for st0012/cctop, covering agents.md - development guide for cctop, scope and sources, required development rules, driver workflow and github and pr rules.
cctop CLAUDE.md
Claude Code instructions for st0012/cctop: This repository keeps shared agent instructions in AGENTS.md. Read AGENTS.md now and follow it as the source of truth for cctop development.
here-macos CLAUDE.md
Instructions for koalaauto/here-macos, covering here — ai assistant notes, architecture at a glance, prerequisites, build & run and always pass -quiet from an agent session.
signalbox CLAUDE.md
Claude Code instructions for dwmkerr/signalbox, covering signalbox, specs are the source of truth - keep them current, layout, build & test and regenerating the hero gif.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
usage CLAUDE.md
Claude Code instructions for aqua5230/usage, covering usage and gotchas.