What is check-pct-formalities?

A checklist for checking whether an international patent application follows the formal rules of the Patent Cooperation Treaty (PCT), an international patent-filing system.

Use it to review a full PCT application or focus on parts such as the request form, description, claims, abstract, drawings, sequence listings, or unity of invention.

It helps find missing sections, formatting problems, language issues, fee problems, and other rule violations before filing.

check-pct-formalities — Command for Claude Code by RobThePCGuy

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/check-pct-formalities/github.svg)](https://agentmods.dev/commands/robthepcguy/claude-patent-creator/check-pct-formalities)

Your own site

<a href="https://agentmods.dev/commands/robthepcguy/claude-patent-creator/check-pct-formalities"><img src="https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/check-pct-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/robthepcguy/claude-patent-creator/check-pct-formalities"><img src="https://agentmods.dev/badge/commands/robthepcguy/claude-patent-creator/check-pct-formalities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 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,378 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.

Model	Per session	Once invoked
Fable 5.1	$0.00022	$0.02378
Opus 5	$0.00011	$0.01189
Sonnet 5	$0.00004	$0.00476
Haiku 4.5	$0.00002	$0.00238

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

Security

Grade A, and why

check-pct-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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

check-pct-formalities — 100% identical, 0 lines differ

commands/check-pct-formalities.md · 290 lines

How it starts

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

PCT Formalities Check

Verify all formal requirements for a PCT international application under PCT Rules 5-12.

Check Type: $ARGUMENTS

What I'll Check

Request Form (Rule 4 PCT) - Form PCT/RO/101, designations, priority claims
Description (Rule 5 PCT) - Required sections, manner of description
Claims (Rule 6 PCT) - Numbering, form, unity of invention (Rule 13 PCT)
Abstract (Rule 8 PCT) - Max 150 words, figure designation
Drawings (Rule 11 PCT) - Technical standards, margins, paper size
Sequence Listings (Rule 12 PCT) - If applicable (WIPO Standard ST.26)
Physical Requirements (Rule 11 PCT) - Paper, margins, font, numbering
Unity of Invention (Rule 13 PCT) - Single general inventive concept
Fees - International filing fee, search fee, transmittal fee
Language (Rule 12 PCT) - Accepted languages per Receiving Office

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

Process

Ask for application sections (or read from file)
Check each PCT formality requirement
Search PCT rules and Administrative Instructions
Generate compliance report with:
- Requirements checklist per rule
- Non-compliance issues with rule citations
- Fix instructions
- Pre-filing checklist for PCT

PCT-Specific Requirements

Request (Rule 4 PCT)

Form PCT/RO/101
Title of invention (same as description)
Applicant details (name, address, nationality, residence)
Agent/representative details (if applicable)
Designation of states (all states designated automatically since 2004)
Priority claims (within 12 months, certified copy required)
Inventor details
Choice of International Searching Authority (ISA)
Reference to deposited biological material (if applicable)

Description (Rule 5 PCT)

Required sections in order:

Title of the invention
Technical field
Background art
Disclosure of the invention (technical problem and solution)
Brief description of drawings (if any)
Best mode for carrying out the invention
Industrial applicability
Sequence listing (if applicable, WIPO Standard ST.26 XML format)

Read the full file on GitHub · 290 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.

10d ago First seen · 290 lines · 22 tokens per session scan A 4e09988ade7b

Subscribe to this mod's changes

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

Claude Code Legal and compliance bigquery claude-code-plugin faiss mcp-server mpep

setup-video-vision

Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.

jordanrendric/claude-video-vision · 20 tokens

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.

avelikiy/great_cto · 81 tokens

check-pct-formalities