figure-description

figure-description is a skill for Claude Code, Codex from Immortalqx/my_codex_skills. It costs 49 tokens per session (1,191 once invoked), scanned A, a copy of figure-description, MIT.

A process for turning user-provided patent drawings into formal descriptions that identify pictured components with reference numbers. Patent figures are technical drawings submitted to help explain an invention and its claims.

In plain words
What is it for?
Use it to process PNG, JPG, SVG, or PDF patent figures and prepare descriptions with numbered components, including notes for required figures that are missing.
Why use it?
It provides consistent figure descriptions and links drawing components to the invention disclosure and patent claims.

Skill for Claude CodeCodex

Written for Claude Code and Codex: $ARGUMENTS substitution, but also agents/openai.yaml present.

Good fit Use it to process PNG, JPG, SVG, or PDF patent figures and prepare descriptions with numbered components, including notes for required figures that are missing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/immortalqx/my_codex_skills/figure-description
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 Immortalqx/my_codex_skills --skill figure-description
Clone the repo
git clone --depth 1 https://github.com/Immortalqx/my_codex_skills

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 figure-description

README.md
[![agentmods](https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/figure-description/github.svg)](https://agentmods.dev/skills/immortalqx/my_codex_skills/figure-description)
Your own site
<a href="https://agentmods.dev/skills/immortalqx/my_codex_skills/figure-description"><img src="https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/figure-description/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 figure-description

Your own site · 80×15
<a href="https://agentmods.dev/skills/immortalqx/my_codex_skills/figure-description"><img src="https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/figure-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,191 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 95% copy Near-identical to another mod 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.00049 $0.01191
Opus 5 $0.00024 $0.00596
Sonnet 5 $0.00010 $0.00238
Haiku 4.5 $0.00005 $0.00119

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

Security

Grade A, and why

figure-description 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 9d 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

This is a copy

95% identical to figure-description — 13 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.

figure-description/SKILL.md · 132 lines

How it starts

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

Figure Description for Patents

Process patent figures and generate drawing descriptions based on: $ARGUMENTS

This skill processes user-provided technical diagrams and assigns reference numerals.

Constants

  • FIGURE_DIR = "patent/figures/" — Output directory for figure descriptions
  • REFERENCE_NUMERAL_PREFIX = 100 — Starting numeral for first figure's components
  • NUMERAL_SERIES = 100 — Each figure uses a separate 100-series (Fig 1: 100-199, Fig 2: 200-299, etc.)

Inputs

  1. User-provided figures (PNG, JPG, SVG, PDF) — search for them in the project directory
  2. patent/INVENTION_DISCLOSURE.md — for understanding what components to identify
  3. patent/CLAIMS.md — for mapping numerals to claim elements

Workflow

Step 1: Discover Figures

  1. Search the project directory for figure files:
    • Check patent/figures/, figures/, root directory
    • Look for PNG, JPG, SVG, PDF files
    • Check INVENTION_BRIEF.md or INVENTION_DISCLOSURE.md for figure references
  2. List all discovered figures with their paths
  3. If figures are missing that claims require, note them as [MISSING: description needed]

Step 2: Analyze Each Figure

For each figure found:

  1. Read the image using the Read tool (supports image files)
  2. Identify components: What labeled or visually distinct components are shown?
  3. Identify connections: How do components relate to each other?
  4. Identify flow: If it's a flowchart or sequence, what is the step order?

Step 3: Assign Reference Numerals

For each figure, assign numerals using the series convention:

Figure Numeral Range
FIG. 1 100-199
FIG. 2 200-299
FIG. 3 300-399

For each identified component: - Assign the next available numeral in the series - Cross-reference to the claim elements it supports - Note if a component appears in multiple figures (use same numeral across figures)

Step 4: Generate Drawing Descriptions

Write formal drawing descriptions (附图说明):

Read the full file on GitHub · 132 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 132 lines · 49 tokens per session scan A 18315df3f07b

Subscribe to this mod's changes

figure-description is a skill published in the GitHub repository Immortalqx/my_codex_skills (52 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,191 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to figure-description, differing in 13 lines, and is treated as a copy.

Related

Other skills, from other repositories

html-ppt-zhangzara-stencil-tablet

A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.

nexu-io/open-design · 49 tokens

treatment-plans

Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…

K-Dense-AI/scientific-agent-skills · 62 tokens

handbook-updates

Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.

anthropics/claude-for-legal · 52 tokens

software-copyright-materials

A workflow for creating Chinese application materials for software copyright registration from a real software project.

Fokkyp/SoftwareCopyright-Skill · 97 tokens

iflytek-contract-intelligence-review

A contract-review workflow for scanned or digital agreements. It can recognize document text, examine clauses, detect risks, check compliance, and create translation summaries; its output is for review and is not formal legal advice.

iflytek/iFly-Skills · 116 tokens

legal-writer

Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification…

kortix-ai/suna · 161 tokens