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.
git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-CreatorWrote 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/commands/robthepcguy/claude-patent-creator/review-specification)<a href="https://agentmods.dev/commands/robthepcguy/claude-patent-creator/review-specification"><img src="https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/review-specification.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.1 | $0.00022 | $0.00339 |
| Opus 5 | $0.00011 | $0.00169 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
review-specification 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- review-specification — 100% identical, 0 lines differ
What it actually says
Specification Review
Check specification for written description, enablement, and best mode requirements.
Focus Area: $ARGUMENTS
What I'll Check
- Written Description (35 USC 112(a)) - Shows you possessed the invention
- Enablement (35 USC 112(a)) - Person skilled in art can make/use it
- Best Mode (35 USC 112(a)) - Preferred embodiment disclosed
- Claim Support - All claim elements described
Specified focus area receives extra detail.
Process
- Ask for specification (or key sections)
- Search MPEP for requirements
- Analyze against 112(a) standards
- Create claim support matrix
- Generate report with:
- Section-by-section analysis
- MPEP citations
- Missing disclosures
- Recommendations
Output
- Written description adequacy assessment
- Enablement scope analysis
- Claim support matrix
- Specific improvements needed
- MPEP references for findings
DISCLAIMER: This tool assists with patent application preparation but does NOT replace legal advice from a registered patent attorney. Always consult with legal counsel before filing. Not affiliated with or endorsed by the USPTO.
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 · 49 lines · 22 tokens per session scan A 39a5e44e995f
review-specification is a command published in the GitHub repository RobThePCGuy/Claude-Patent-Creator (179 stars, last pushed 15d ago), licensed MIT. It adds 22 tokens to every session and 339 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-30.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
search-flights
Search award flight availability across airlines.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
pillar-guidance
Deep dive guidance on DORA's 5 pillars and implementation requirements.