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/sean-galloway/rtldesignsherpa/module-docsnpx skills add sean-galloway/RTLDesignSherpa --skill module-docsgit 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/skills/sean-galloway/rtldesignsherpa/module-docs)<a href="https://agentmods.dev/skills/sean-galloway/rtldesignsherpa/module-docs"><img src="https://agentmods.dev/badge/skills/sean-galloway/rtldesignsherpa/module-docs.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.00088 | $0.00456 |
| Opus 5 | $0.00044 | $0.00228 |
| Sonnet 5 | $0.00018 | $0.00091 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
module-docs 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
module-docs
READ FIRST: vault/handbook/INDEX.md (the handbook is the repo's memory; this skill is the signpost). Canonical: vault/handbook/authoring/module-doc-template.md - the section structure every per-module page follows, plus the SV header block that mirrors it.
The rules that get violated most:
- One source per fact. A port list / parameter table stated in both the
.svand the.mdrots. State it once; when you change ports, update BOTH in the same commit (the.svheader and the.mdinterface block). - Follow an existing sibling. New
docs/markdown/rtl-amba/monitor/*.mdpages copy the header table and section order of a peer (e.g.monbus_compressor.md), not a blank template. - Keep the book index in sync. A new page MUST be linked from its
_book_<area>_index.md(e.g.docs/markdown/rtl-amba/_book_monitor_index.md), or the generated PDF book never includes it. - No emojis in pipeline docs - they break the LaTeX/PDF path. See [[doc-pipeline]].
- Placement rules (which .md lives where) are a separate concern - see the
doc-placementskill / [[doc-placement]].
The handbook root is vault/handbook/INDEX.md - design/, dv/, fpga/, authoring/ areas, atomic notes, wikilinked. When you learn a durable lesson in this domain, ADD IT TO THE HANDBOOK NOTE ([[module-doc-template]]), not to this 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.
- 5d ago First seen · 29 lines · 88 tokens per session scan A e377904c94e1
module-docs is a skill published in the GitHub repository sean-galloway/RTLDesignSherpa (23 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 456 once invoked, about $0.0004 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 skills, from other repositories
vdoc
Aggregate all per-module documentation into a single comprehensive IP document.
datasheets
Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Cache extractions per project for consumption by schematic and PCB analyzers. Primary consumer infrastructure for kicad, emc, spice, and thermal analyzers. Use this…
readable-verilog-generator
Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed…
003-skills-inventory
Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory…
001-commands-inventory
Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use…
002-agents-inventory
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use…