Borrowing it
Nothing to install: this file belongs to sean-galloway/RTLDesignSherpa. 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/sean-galloway/RTLDesignSherpa/main/CLAUDE.mdgit clone --depth 1 https://github.com/sean-galloway/RTLDesignSherpaWrote 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/sean-galloway/rtldesignsherpa/claude-md)<a href="https://agentmods.dev/instructions/sean-galloway/rtldesignsherpa/claude-md"><img src="https://agentmods.dev/badge/instructions/sean-galloway/rtldesignsherpa/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/sean-galloway/rtldesignsherpa/claude-md"><img src="https://agentmods.dev/badge/instructions/sean-galloway/rtldesignsherpa/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.04785 | $0.04785 |
| Opus 5.5 | $0.01914 | $0.01914 |
| Sonnet 5.5 | $0.00957 | $0.00957 |
| Haiku 4.5 | $0.00479 | $0.00479 |
Grade A, and why
RTLDesignSherpa 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Guide for RTL Design Sherpa
Version: 1.3 Last Updated: 2026-09-20 Purpose: Help Claude Code work efficiently with this repository
The Handbook (repo memory) - READ THIS FIRST
vault/handbook/INDEX.md is the SINGLE SOURCE OF TRUTH for every skill and
method in this repository. It is the repo's working memory: design rules
(design/), DV practice (dv/), FPGA process (fpga/), and documentation
practice (authoring/) as atomic, wikilinked notes - each rule recorded WITH
the failure that taught it.
- Skills (
.claude/skills/, auto-discovered) are signposts only. A skill names its canonical handbook note and stops. Method detail does not live in a skill file. - Methodology does not live next to the code. No
README.mdbeside a tool restating how to use it, no how-to in a docstring beyond what a reader of that one file needs, and no canonical process document outside the repo. A second copy is how documentation rots - the copy nobody edits is the one the next session reads. Point at the handbook note instead. The one exception (Sean, 2026-09-25): TOOL MECHANICS may live beside the tool, with the rationale in the handbook.bin/DOC_GENERATION.md,bin/SIGNAL_CONTRACTS_KMAPS.mdandbin/SIGNAL_NAMING_AUDIT.mdstay where they are, and [[doc-pipeline]] and [[signal-contracts-and-kmaps]] keep pointing outward at them. The test is whether the file carries mechanics a reader of that directory needs -- the 6-step stand-up, the styles YAML, the flags -- or method that applies everywhere, which still belongs in the handbook. The same test applies to a subsystem CLAUDE.md: area-specific mechanics stay, restated general method goes. - /GLOBAL_REQUIREMENTS.md remains the enforcement authority and wins on conflict.
- When you learn a durable lesson, add it to the relevant handbook note - that is where future sessions will look. If no note fits, create one and index it; do not park the lesson in a CLAUDE.md or a skill.
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 Changed · +2 tokens per session 1c9dffa09db7
- 15d ago Changed · +2 tokens per session 441ff2db044f
- 28d ago Changed · +70 tokens per session a7d7d9e481f1
- 1mo ago Changed · +9 lines · +177 tokens per session f2369c7eb807
- 1mo ago Changed · +31 lines · +579 tokens per session 067163bb74fb
- 1mo ago Changed · +15 lines · +218 tokens per session 27d53e90eb90
- 1mo ago Changed · -624 lines · -5,288 tokens per session e1cc5b803ea8
- 1mo ago First seen · 1,033 lines · 9,025 tokens per session scan A 66e1854c4d5e
RTLDesignSherpa CLAUDE.md is an instructions file published in the GitHub repository sean-galloway/RTLDesignSherpa (25 stars, last pushed 2d ago), licensed MIT. It adds 4,785 tokens to every session, about $0.0191 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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.