Borrowing it
Nothing to install: this file belongs to edosulai/silenthand-cua. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/edosulai/silenthand-cua/main/CLAUDE.mdgit clone --depth 1 https://github.com/edosulai/silenthand-cuaWrote 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/edosulai/silenthand-cua/claude-md)<a href="https://agentmods.dev/instructions/edosulai/silenthand-cua/claude-md"><img src="https://agentmods.dev/badge/instructions/edosulai/silenthand-cua/claude-md/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/instructions/edosulai/silenthand-cua/claude-md"><img src="https://agentmods.dev/badge/instructions/edosulai/silenthand-cua/claude-md.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.00440 | $0.00440 |
| Opus 5 | $0.00220 | $0.00220 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
silenthand-cua 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 8d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
graphify
This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
Rules:
- For codebase questions, first run
graphify query "<question>"when graphify-out/graph.json exists. Usegraphify path "<A>" "<B>"for relationships andgraphify explain "<concept>"for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output. - If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
- After modifying code, run
graphify update .to keep the graph current (AST-only, no API cost).
Public repo hygiene
This repo may become public. Commits, commit messages, tags, and git history are visible forever. .gitignore only protects the next commit. A clean working tree is not a clean history.
Never commit live identity or machine-local state:
- secrets, tokens, API keys,
.env, credentials, session/auth dirs - real phone numbers, emails, home paths (
/Users/...), hostnames, internal URLs - generated caches, build output, editor/vendor skill folders, local graphs, logs
Public docs and tests use fake placeholders only. Copy from *.example files. Do not put live ids, real names of private accounts, or personal paths back into comments, fixtures, or commit messages.
Before every commit:
- Check
git status. Ignored local files must stay untracked. - Do not stage generate, cache, or vendor folders even if they look dirty.
- Scan the staged diff for secrets, personal identifiers, and absolute local paths.
If a secret already landed in git, say so and wait for an explicit history-rewrite request. Do not force-push on your own.
Do not start extra services, mint pairing/auth artifacts, or touch live user accounts unless the user asked. In chat, use aliases — not raw personal identifiers.
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.
- 8d ago First seen · 30 lines · 440 tokens per session scan A 71304f76bdce
silenthand-cua CLAUDE.md is an instructions file published in the GitHub repository edosulai/silenthand-cua (0 stars, last pushed 7d ago), licensed MIT. It adds 440 tokens to every session, about $0.0022 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.