Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Raw1mage/patentmcp/plugin install claude-patent-creator-standaloneWrote 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/raw1mage/patentmcp/review-claims)<a href="https://agentmods.dev/commands/raw1mage/patentmcp/review-claims"><img src="https://agentmods.dev/badge/commands/raw1mage/patentmcp/review-claims/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/commands/raw1mage/patentmcp/review-claims"><img src="https://agentmods.dev/badge/commands/raw1mage/patentmcp/review-claims.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.00023 | $0.02422 |
| Opus 5 | $0.00012 | $0.01211 |
| Sonnet 5 | $0.00005 | $0.00484 |
| Haiku 4.5 | $0.00002 | $0.00242 |
Grade A, and why
review-claims 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 10d 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.
This is a copy
100% identical to review-claims — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Patent Claims
Automated analysis of patent claims for USPTO compliance with detailed issue reporting and fixes.
What This Command Does
Performs comprehensive automated claims analysis:
-
Antecedent Basis Checking:
- Finds terms used without prior introduction
- Detects "said/the" used before "a/an"
- Tracks term usage across claims
-
Definiteness Analysis (35 USC 112(b)):
- Identifies subjective/indefinite terms
- Detects relative terms without reference
- Finds ambiguous language
-
Claim Structure Validation:
- Parses independent vs. dependent claims
- Validates dependencies
- Checks claim numbering
-
Issue Categorization:
- Critical: Must fix before filing
- Important: May cause rejection
- Minor: Best practice improvements
Who This Is For
- Patent attorneys reviewing draft claims
- Inventors before filing
- Responding to 112(b) office action rejections
- Quality assurance before USPTO submission
Process
Step 1: Provide Claims
You can provide claims in three ways:
Option 1: Paste claims directly
/review-claims
> Paste your claims text, then type 'END' on a new line:
What is claimed is:
1. A system comprising:
a processor;
a memory; and
said processor configured to execute instructions.
END
Option 2: Point to a file
/review-claims path/to/claims.txt
Option 3: Let me read from current conversation
[You paste claims in chat]
/review-claims --from-context
Step 2: Automated Analysis
I'll run the claims through the automated analyzer:
from python.claims_analyzer import ClaimsAnalyzer
analyzer = ClaimsAnalyzer()
results = analyzer.analyze_claims(claims_text)
This checks:
- All terms for antecedent basis
- All language for definiteness
- Claim structure and dependencies
- Cross-references and pointers
Step 3: Generate Report
I'll provide a detailed compliance report with:
- Overall compliance score (0-100)
- Issue count by severity
- Specific issues with locations
- MPEP citations
- Suggested fixes
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.
- 10d ago First seen · 420 lines · 23 tokens per session scan A b4deec6b30bb
review-claims is a command published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 2,422 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-claims, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
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.
msp-review
MSP / managed-services compliance check — invokes msp-reviewer to produce TM-msp-{slug}.md with client-isolation, credential-vaulting, SLA-tracking, and incident-escalation gaps.
procurement-review
Procurement / source-to-pay compliance check — invokes procurement-reviewer to produce TM-procurement-{slug}.md with three-way match, segregation-of-duties, OFAC-screening, and SOX procurement-controls gaps.
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.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.