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 Immortalqx/my_codex_skills --skill figure-descriptiongit clone --depth 1 https://github.com/Immortalqx/my_codex_skillsWrote 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/immortalqx/my_codex_skills/figure-description)<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.
<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>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.00049 | $0.01191 |
| Opus 5 | $0.00024 | $0.00596 |
| Sonnet 5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
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.
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.
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 descriptionsREFERENCE_NUMERAL_PREFIX = 100— Starting numeral for first figure's componentsNUMERAL_SERIES = 100— Each figure uses a separate 100-series (Fig 1: 100-199, Fig 2: 200-299, etc.)
Inputs
- User-provided figures (PNG, JPG, SVG, PDF) — search for them in the project directory
patent/INVENTION_DISCLOSURE.md— for understanding what components to identifypatent/CLAIMS.md— for mapping numerals to claim elements
Workflow
Step 1: Discover Figures
- 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
- Check
- List all discovered figures with their paths
- If figures are missing that claims require, note them as
[MISSING: description needed]
Step 2: Analyze Each Figure
For each figure found:
- Read the image using the Read tool (supports image files)
- Identify components: What labeled or visually distinct components are shown?
- Identify connections: How do components relate to each other?
- 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 (附图说明):
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.
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.
- 9d ago First seen · 132 lines · 49 tokens per session scan A 18315df3f07b
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.
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.
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…
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.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.
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.
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…