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/gabrielmoreira/agent-skills-mirrorWrote 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/rules/gabrielmoreira/agent-skills-mirror/paper2patent)<a href="https://agentmods.dev/rules/gabrielmoreira/agent-skills-mirror/paper2patent"><img src="https://agentmods.dev/badge/rules/gabrielmoreira/agent-skills-mirror/paper2patent/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/rules/gabrielmoreira/agent-skills-mirror/paper2patent"><img src="https://agentmods.dev/badge/rules/gabrielmoreira/agent-skills-mirror/paper2patent.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00173 |
| Opus 5 | $0.00013 | $0.00086 |
| Sonnet 5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
paper2patent 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 7d 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 paper2patent — 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.
What it actually says
- Use
skills/paper2patent/SKILL.mdas the canonical workflow for paper-to-patent tasks. - Keep long drafting rules in
skills/paper2patent/references/; do not duplicate full templates in IDE rule files. - Preserve fidelity to the supplied paper. Do not invent technical details, embodiments, metrics, or effects.
- Do not commit unpublished papers, generated patent drafts, personal data, API keys, tokens, local usernames, or local absolute paths.
- When editing skill files, validate both
skills/paper2patentand.claude/skills/paper2patentif the Claude mirror exists.
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.
- 7d ago First seen · 12 lines · 26 tokens per session scan A 1fdcfb5ddba0
paper2patent is a cursor rule published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 173 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 paper2patent, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.