review-epo-formalities

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

A command that checks European patent applications against formal requirements set by the European Patent Office, or EPO, the organization handling European patent applications.

In plain words
What is it for?
Use it to review application formalities under EPC Rules 42–49, generate a rule-based compliance report, and prepare a pre-filing checklist.
Why use it?
It helps find missing or incorrect sections, claims, drawings, translations, and fees before filing.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

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

Good fit Use it to review application formalities under EPC Rules 42–49, generate a rule-based compliance report, and prepare a pre-filing checklist.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/robthepcguy/claude-patent-creator/review-epo-formalities
Install

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.

Clone the repo
git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator

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-epo-formalities

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/robthepcguy/claude-patent-creator/review-epo-formalities"><img src="https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/review-epo-formalities.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 1,767 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.01767
Opus 5 $0.00012 $0.00883
Sonnet 5 $0.00005 $0.00353
Haiku 4.5 $0.00002 $0.00177

Measured 11d ago against content hash 5960e4088721, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

review-epo-formalities 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 11d 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-epo-formalities.md · 225 lines

How it starts

The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.

EPO Formalities Check

Verify all formal requirements for a European patent application under EPC Rules 42-49.

Check Type: $ARGUMENTS

What I'll Check

  1. Description (Rule 42 EPC) - Required sections, disclosure sufficiency, unity
  2. Claims (Rule 43 EPC) - Two-part form, numbering, fees for excess claims
  3. Abstract (Rule 47 EPC) - Max 150 words, single figure designation, content
  4. Drawings (Rule 46 EPC) - Technical quality, reference signs, margins
  5. Request for Grant (Rule 41 EPC) - Form 1001, designation of states, priorities
  6. Translation Requirements - Language of proceedings (Rule 6 EPC)
  7. Fees - Filing fee, search fee, designation fee, claims fee (> 15 claims)

Specified check type focuses on that requirement; otherwise checks everything.

Process

  1. Ask for application sections (or read from file)
  2. Check each EPO formality requirement
  3. Search EPC rules and EPO Guidelines for standards
  4. Generate compliance report with:
    • Requirements checklist per rule
    • Non-compliance issues
    • Fix instructions with rule citations
    • Pre-filing checklist for EPO

EPO-Specific Requirements

Description (Rule 42 EPC)

Required sections in order:

  • Title of the invention
  • Technical field
  • Background art (with citation of prior art documents)
  • Disclosure of the invention (technical problem and solution)
  • Brief description of drawings (if any)
  • Detailed description of at least one embodiment
  • Industrial applicability (if not obvious)

Claims (Rule 43 EPC)

  • Two-part form for independent claims (preamble + "characterised in that")
  • Clear reference to description and drawings
  • No drawings or graphs in claims
  • Numbered consecutively in Arabic numerals
  • Fee applies for each claim beyond 15 (Rule 45 EPC)
  • Fee applies for each claim beyond 50

Abstract (Rule 47 EPC)

  • Maximum 150 words
  • Must indicate technical field
  • Must include concise summary of disclosure
  • Must designate most illustrative figure (if drawings exist)
  • No commercial statements
  • Single paragraph preferred

Read the full file on GitHub · 225 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. 11d ago First seen · 225 lines · 23 tokens per session scan A 5960e4088721

Subscribe to this mod's changes

review-epo-formalities is a command published in the GitHub repository RobThePCGuy/Claude-Patent-Creator (180 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 1,767 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.