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/Raw1mage/patentmcpWrote 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/check-pct-formalities)<a href="https://agentmods.dev/commands/raw1mage/patentmcp/check-pct-formalities"><img src="https://agentmods.dev/badge/commands/raw1mage/patentmcp/check-pct-formalities.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.02378 |
| Opus 5 | $0.00011 | $0.01189 |
| Sonnet 5 | $0.00004 | $0.00476 |
| Haiku 4.5 | $0.00002 | $0.00238 |
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 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.
This is a copy
100% identical to check-pct-formalities — 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 — 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)
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 · 290 lines · 22 tokens per session scan A 4e09988ade7b
check-pct-formalities is a command published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), 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. It is 100% identical to check-pct-formalities, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
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.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.