kr-patent-full-workflow

kr-patent-full-workflow is a skill for Claude Code, Codex from lsj4232/KR_PATENT_SKILL. It costs 305 tokens per session (8,137 once invoked), scanned A, original, MIT.

A coordinator for writing a Korean patent specification from start to finish. It guides the work through invention interviews, claim preparation, technical details, consistency checks, and final DOCX output.

In plain words
What is it for?
Use it to run the complete Korean patent-writing process, from inventor input and claim refinement to a finished Word document.
Why use it?
It reduces the risk of missing a stage when preparing one patent document and keeps the related specialist steps in order.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to run the complete Korean patent-writing process, from inventor input and claim refinement to a finished Word document.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lsj4232/kr_patent_skill/kr-patent-full-workflow
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.

Any agent
npx skills add lsj4232/KR_PATENT_SKILL --skill kr-patent-full-workflow
Clone the repo
git clone --depth 1 https://github.com/lsj4232/KR_PATENT_SKILL

Made for: Claude Code, Codex.

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 kr-patent-full-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/lsj4232/kr_patent_skill/kr-patent-full-workflow/github.svg)](https://agentmods.dev/skills/lsj4232/kr_patent_skill/kr-patent-full-workflow)
Your own site
<a href="https://agentmods.dev/skills/lsj4232/kr_patent_skill/kr-patent-full-workflow"><img src="https://agentmods.dev/badge/skills/lsj4232/kr_patent_skill/kr-patent-full-workflow/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 kr-patent-full-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/lsj4232/kr_patent_skill/kr-patent-full-workflow"><img src="https://agentmods.dev/badge/skills/lsj4232/kr_patent_skill/kr-patent-full-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 305 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,137 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00305 $0.08137
Opus 5 $0.00152 $0.04068
Sonnet 5 $0.00061 $0.01627
Haiku 4.5 $0.00030 $0.00814

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

Security

Grade A, and why

kr-patent-full-workflow 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.

kr-patent-full-workflow/SKILL.md · 603 lines

How it starts

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

한국 특허 명세서 전체 워크플로우 (오케스트레이터)

무엇을 하는가

다른 8개 kr-patent-* 스킬을 적절한 순서로 호출하여 명세서 한 건을 처음부터 끝까지 진행한다. 변리사가 "이번 건 하나 끝까지 도와줘"라고 했을 때, 단계별로 빠뜨림 없이 진행하는 체크리스트 + 진행 추적 도구다.

이 스킬은 직접 산출물을 만들지 않고, 다른 8개 스킬을 적절히 호출만 한다. 오케스트레이터 역할.

전체 워크플로우 (11단계)

┌─────────────────────────────────────────────────────────┐
│ Stage 0: 입력 점검 + 기술분야 프로파일 판정 (G / H / 혼합)     │
│          — 어느 단계부터 시작할지 판단                       │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 1: 발명자 미팅 질문 생성 (선택)                       │
│ → kr-patent-inventor-meeting                            │
└──────────────────────────────┬──────────────────────────┘
                               │ (미팅 후 청구항 확정 대기)
┌──────────────────────────────▼──────────────────────────┐
│ Stage 2: 청구항 확정 확인 — 사용자가 청구항 제공            │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 3: 부호 체계 설계                                  │
│ → kr-patent-symbol-design                               │
│ ★ 체크포인트: 사용자 OK 받기                              │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 4: 스토리텔링 설계 (배경→과제→수단→효과 큰 흐름)         │
│ → kr-patent-spec-drafting (Step 3)                      │
│ ★ 체크포인트: 사용자 OK 받기                              │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 5: 명세서 본문 작성 (1차 초안)                       │
│ → kr-patent-spec-drafting (Step 4-6)                    │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 6: 권리범위 보강 — 용어 정의 삽입 ★ 체크포인트          │
│ → kr-patent-definition-insertion                        │
│ → 청구항 한정 용어 자체 사전 정의 인라인 삽입               │
│   (모드 A) 단일 용어 정의 — (i)(ii)(iii) 3요소 골격         │
│   (모드 B) 열거 항목 풀이 — 나열된 노드·관계·소스 개별 단락   │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 6.5: 권리범위 보강 — 구성요소·파이프라인 구체화 ★      │
│ → kr-patent-implementation-elaboration                  │
│   (모드 A) 각 ~부/~모듈에 판단 기준 3단(기준→적용→효과)      │
│   (모드 B) 시스템 전체 데이터 처리 파이프라인 통합 단락       │
│   (provenance flag · 식별자 연계)                        │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 7: 권리범위 보강 — 변형 실시예 추가 ★ 체크포인트        │
│ → kr-patent-embodiment-addition                         │
│ → 기술 도메인 16카테고리 + 설계 결정 8축(D1~D8) 직교 적용     │
│ → 절별 도메인 4~7개 + 설계 3~5개 변형 단락 부가             │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 8: 정합성 점검                                     │
│ → kr-patent-consistency-check                           │
│ → 점수 + 수정안                                          │
│ ★ 체크포인트: 어떤 수정 적용할지 사용자 결정                  │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 9: 수정 반영                                       │
│ → kr-patent-spec-drafting (수정 모드)                    │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 10: docx 출력                                      │
│ → kr-patent-docx-builder                                │
└──────────────────────────────┬──────────────────────────┘
                               │
┌──────────────────────────────▼──────────────────────────┐
│ Stage 11: 회고 → 학습 항목 누적 (선택)                      │
│ → kr-patent-skill-updater                               │
└─────────────────────────────────────────────────────────┘

Read the full file on GitHub · 603 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 · 603 lines · 305 tokens per session scan A 8c75ade7eb2e

Subscribe to this mod's changes

kr-patent-full-workflow is a skill published in the GitHub repository lsj4232/KR_PATENT_SKILL (14 stars, last pushed 17d ago), licensed MIT. It adds 305 tokens to every session and 8,137 once invoked, about $0.0015 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.

Related

Other skills, from other repositories

document-fill

A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.

code-lawyer/Legal-Agent-Skills · 61 tokens

nuremberg-tokyo

Post-WWII international military tribunals research, drafting, and analysis: the IMT at Nuremberg (1945-46), the twelve NMT trials under Control Council Law No. 10 (1946-49), and the IMTFE at Tokyo (1946-48). Use whenever the conversation involves Nuremberg, the Tokyo Trial, the London or Tokyo Charters, the IMT or…

jeannesulzer/international-criminal-tribunals-skills · 0 tokens

cps-rca

Cour Pénale Spéciale de la République Centrafricaine (CPS) / Special Criminal Court in the Central African Republic (SCC-CAR) research, drafting, and analysis. Use whenever the conversation involves the CPS, the Loi organique n°15.003 of 3 June 2015, the RPP (Loi 18.010), the affaire Paoua / Lemouna et Koundjili (Issa…

jeannesulzer/international-criminal-tribunals-skills · 0 tokens

eac-habre

Chambres Africaines Extraordinaires (CAE) / Extraordinary African Chambers in the Courts of Senegal (EAC) research, drafting, and analysis — the Hissène Habré case. Use whenever the conversation involves the CAE/EAC, the AU-Senegal Accord of 22 August 2012, the Statute of the Chambers, the Habré trial (2015-2016), the…

jeannesulzer/international-criminal-tribunals-skills · 0 tokens

eccc

Extraordinary Chambers in the Courts of Cambodia (ECCC, Khmer Rouge Tribunal) research, drafting, and analysis. Use whenever the conversation involves the ECCC, Case 001 (Duch), Case 002 (NUON Chea, KHIEU Samphan) including the severance into Cases 002/01 and 002/02, Cases 003 and 004, the ECCC Law, the Internal…

jeannesulzer/international-criminal-tribunals-skills · 0 tokens

jep

Jurisdicción Especial para la Paz (JEP) — Colombia's Special Jurisdiction for Peace — research, drafting, and analysis. Use whenever the conversation involves the JEP, the SIVJRNR / Sistema Integral para la Paz, the 2016 Final Peace Agreement with the FARC-EP, Acto Legislativo 01 de 2017, Ley Estatutaria 1957 de 2019…

jeannesulzer/international-criminal-tribunals-skills · 0 tokens