review-claims

review-claims is a command for Claude Code from RobThePCGuy/Claude-Patent-Creator. It costs 23 tokens per session (2,422 once invoked), scanned A, original, MIT.

A command that checks patent claims for issues under 35 U.S.C. §112(b), a U.S. patent rule requiring claims to be clear and definite. It examines whether terms were introduced properly, whether wording is ambiguous, and whether claim dependencies and numbering are valid.

In plain words
What is it for?
Use it to review draft claims, classify issues by severity, and identify changes for patent attorneys, inventors, or filing-quality checks.
Why use it?
It helps find unclear or structurally incorrect claim language before filing with the U.S. Patent and Trademark Office or responding to an examiner’s objection.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-patent-creator-standalone plugin — 17 skills, 16 commands, 13 agents, 2 hooks shipped together

Good fit Use it to review draft claims, classify issues by severity, and identify changes for patent attorneys, inventors, or filing-quality checks.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add RobThePCGuy/Claude-Patent-Creator
Claude Code
/plugin install claude-patent-creator-standalone

Made for: Claude Code.

Or install claude-patent-creator-standalone, the plugin that ships this one along with the rest of its 17 skills, 16 commands, 13 agents, 2 hooks.

Wrote 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.

agentmods badge for review-claims

README.md
[![agentmods](https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/review-claims/github.svg)](https://agentmods.dev/commands/robthepcguy/claude-patent-creator/review-claims)
Your own site
<a href="https://agentmods.dev/commands/robthepcguy/claude-patent-creator/review-claims"><img src="https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/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.

agentmods 80×15 button for review-claims

Your own site · 80×15
<a href="https://agentmods.dev/commands/robthepcguy/claude-patent-creator/review-claims"><img src="https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/review-claims.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,422 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 13d ago against content hash b4deec6b30bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 13d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

commands/review-claims.md · 420 lines

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:

  1. Antecedent Basis Checking:

    • Finds terms used without prior introduction
    • Detects "said/the" used before "a/an"
    • Tracks term usage across claims
  2. Definiteness Analysis (35 USC 112(b)):

    • Identifies subjective/indefinite terms
    • Detects relative terms without reference
    • Finds ambiguous language
  3. Claim Structure Validation:

    • Parses independent vs. dependent claims
    • Validates dependencies
    • Checks claim numbering
  4. 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

Read the full file on GitHub · 420 lines

Changes

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.

  1. 13d ago First seen · 420 lines · 23 tokens per session scan A b4deec6b30bb

Subscribe to this mod's changes

review-claims is a command published in the GitHub repository RobThePCGuy/Claude-Patent-Creator (183 stars, last pushed 3d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.