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.
npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-application-creatorgit clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-CreatorWrote 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/skills/robthepcguy/claude-patent-creator/patent-application-creator)<a href="https://agentmods.dev/skills/robthepcguy/claude-patent-creator/patent-application-creator"><img src="https://agentmods.dev/badge/skills/robthepcguy/claude-patent-creator/patent-application-creator/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/skills/robthepcguy/claude-patent-creator/patent-application-creator"><img src="https://agentmods.dev/badge/skills/robthepcguy/claude-patent-creator/patent-application-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00087 | $0.04137 |
| Opus 5 | $0.00044 | $0.02069 |
| Sonnet 5 | $0.00017 | $0.00827 |
| Haiku 4.5 | $0.00009 | $0.00414 |
Grade A, and why
patent-application-creator 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.
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patent Application Creator Skill
Run a complete patent campaign: take whatever the user has — a codebase, an invention disclosure, scattered notes — and either produce a filing-ready provisional package or a reasoned, evidence-backed explanation of why not.
This workflow was hardened by running it for real (a full campaign over a production codebase, July 2026). Every phase below exists because skipping it cost something in that campaign.
The contract
- The honest outcome is the deliverable. "Nothing here clears the novelty bar, and here is the prior art that kills each candidate" is a SUCCESS, not a failure. So is "this is patentable but not worth your money — file nothing, or publish defensively." Never inflate a weak candidate.
- The campaign guards the user's money, not just their filing. The population this tool serves cannot afford a technically perfect package for a commercially worthless patent. The worth-it question is asked BEFORE the expensive phases and re-asked every time the claims narrow — a campaign that only discovers "small fence" at the end has already spent the user's budget answering the wrong question.
- Machine checks gate, humans verify. Every automated finding marked LOW confidence gets manual verification; every clean bill of health names the checks that ran AND the checks that were skipped.
- Dates matter. Prior art is being published continuously; note recency threats found during the sweep and say so in the package. Filing sooner beats polishing longer for a provisional.
- The AI is never the inventor. The user is. The AI mines, searches, drafts, and verifies; the user's creation is what gets protected.
Phase 0 — Intake (any raw material)
Accept the rough ask as-is. If the material is a codebase, do NOT ask for a disclosure — mining is Phase 1's job. Ask only what cannot be derived: inventor name(s), and whether any of it has been publicly disclosed or sold (statutory bar dates). Then AUDIT the inventor's own public footprint — released products, demos, public repositories, marketing pages — and record first-disclosure dates: the inventor's own disclosures start the US grace-period clock and can immediately forfeit foreign rights. Do this before drafting, not after.
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 · 324 lines · 87 tokens per session scan A 41eece3674cc
patent-application-creator is a skill published in the GitHub repository RobThePCGuy/Claude-Patent-Creator (180 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 4,137 once invoked, about $0.0004 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.
Other skills, from other repositories
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
video-perception
Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content…