glossary-extract

glossary-extract is a skill for Claude Code, Codex from reem-sab/tech-writer-prompts. It costs 107 tokens per session (787 once invoked), scanned A, original, MIT.

A documentation review that finds repeated specialist terms left undefined across one or more pages and drafts definitions from their surrounding text.

In plain words
What is it for?
Use it to review documentation, identify glossary gaps, and prepare definitions for editorial approval.
Why use it?
It shows which glossary entries are missing and ranks them by how often the terms appear, so you can decide what to define first.

Skill for Claude CodeCodex

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

Good fit Use it to review documentation, identify glossary gaps, and prepare definitions for editorial approval.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/reem-sab/tech-writer-prompts/glossary-extract
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 reem-sab/tech-writer-prompts --skill glossary-extract
Clone the repo
git clone --depth 1 https://github.com/reem-sab/tech-writer-prompts

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 glossary-extract

README.md
[![agentmods](https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/glossary-extract/github.svg)](https://agentmods.dev/skills/reem-sab/tech-writer-prompts/glossary-extract)
Your own site
<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/glossary-extract"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/glossary-extract/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 glossary-extract

Your own site · 80×15
<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/glossary-extract"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/glossary-extract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 787 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 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.00107 $0.00787
Opus 5 $0.00053 $0.00394
Sonnet 5 $0.00021 $0.00157
Haiku 4.5 $0.00011 $0.00079

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

Security

Grade A, and why

glossary-extract 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 12d 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.

prompts/glossary-extract/SKILL.md · 84 lines

How it starts

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

Glossary Extract

Scans a set of pages for domain-specific terms that are used repeatedly but never actually defined, ranks them by frequency, and drafts a definition for each from context, so you get a prioritized list of what to add to the glossary instead of starting from a blank page.

Inputs

  • {{PAGES}}: One or more documentation pages, concatenated. If from multiple files, separate them with a line like "--- ---" so the output can cite where each term first appears.

How to apply

Substitute each {{PLACEHOLDER}} above with the user's actual content, then follow the prompt below exactly — including its output format and its stated limits.


You are building a glossary by finding the gaps in one: every domain- specific term used across PAGES that is never explicitly defined anywhere in them.

What counts as a term

A domain-specific noun, acronym, or short phrase specific to this product or its problem space — not a common English word, not a generic software term every reader already knows (API, endpoint, JSON don't count unless PAGES uses them in a specific, non-standard way). If in doubt whether a reader outside this product would already know the term, it probably doesn't belong in the glossary.

What counts as "defined"

The term is used with an explicit definition somewhere in PAGES — a sentence that states what it is, not just a sentence that uses it in context. "A subscription is a standing request to receive events matching a filter" is a definition. Five sentences that each use "subscription" in a different code sample are not.

If a term is defined once but used many more times, it does not belong in the output — it only qualifies if it is undefined everywhere it appears.

Method

  1. Scan PAGES for candidate terms.
  2. For each candidate, check every occurrence — if none of them define it, it's undefined.
  3. Count occurrences (frequency) and note where it first appears.
  4. Draft a definition using only what context across PAGES implies about the term — do not use outside knowledge of what a term like this "usually" means in other products.

Read the full file on GitHub · 84 lines

Files

What ships with it

4 files 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. 12d ago First seen · 84 lines · 107 tokens per session scan A 29a4512163db

Subscribe to this mod's changes

glossary-extract is a skill published in the GitHub repository reem-sab/tech-writer-prompts (4 stars, last pushed 13d ago), licensed MIT. It adds 107 tokens to every session and 787 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens