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 skills/danielrmay/claudity/embednpx skills add danielrmay/claudity --skill embedgit clone --depth 1 https://github.com/danielrmay/claudityWhat 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.00022 | $0.01375 |
| Opus 5 | $0.00011 | $0.00687 |
| Sonnet 5 | $0.00004 | $0.00275 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
embed 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embed the Clarity Protocol into the current project. Both steps are idempotent — safe to re-run.
-
Scaffold the protocol directory:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/protocol_init.py" .This creates
.clarity-protocol/(orClarity Protocol/outside git repos) with template documents,config.json, and the suggestions mailbox, skipping anything that already exists. -
Install the snippet into CLAUDE.md: take the template between the
SNIPPET-TEMPLATEmarkers below (exclusive), replace every{{PROTOCOL_DIR_NAME}}with the actual protocol directory name from step 1, and place the result in the project's rootCLAUDE.md:- If
CLAUDE.mddoesn't exist, create it with the snippet as its content. - If it exists and contains a
<!-- claudity-begin -->...<!-- claudity-end -->block, replace that block (and only that block) with the new snippet. - Otherwise append the snippet to the end, separated by a blank line. Never modify content outside the markers.
- If
-
Confirm briefly what was created, then offer to start: the user can run
/claudity:startor just begin talking about the project. The protocol directory is meant to be committed and reviewed like any other source file.
Clarity Protocol
This project uses the Clarity Protocol for structured thinking about consequential decisions — what to build and why, how it should be designed, where it might fail. Protocol documents live in {{PROTOCOL_DIR_NAME}}/. The Claudity plugin provides the Clarity MCP tools (clarity-agent server) and skills (/claudity:start, /claudity:status, and friends). Use its tools to interact with the protocol — do not try to install or run Clarity directly.
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.
- 2d ago First seen · 60 lines · 22 tokens per session scan A d2c989fb6de9
embed is a skill published in the GitHub repository danielrmay/claudity (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,375 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…