glossary

glossary is a command for Claude Code from Abhinavbwj/AEC-Scholar. It costs 17 tokens per session (383 once invoked), scanned A, original, MIT.

A command for creating an alphabetical glossary of terms used in architecture, engineering, and construction (AEC) papers or theses.

In plain words
What is it for?
Extracting terms from text or listing key concepts for a topic, then presenting definitions and relevant standards in a table.
Why use it?
It helps readers understand specialised terms, abbreviations, and concepts, including meanings that differ across standards or research literature.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the aec-scholar plugin — 11 skills, 36 commands, 10 agents, 1 hook shipped together

Good fit Extracting terms from text or listing key concepts for a topic, then presenting definitions and relevant standards in a table.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/abhinavbwj/aec-scholar/glossary
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.

Clone the repo
git clone --depth 1 https://github.com/Abhinavbwj/AEC-Scholar

Made for: Claude Code.

Or install aec-scholar, the plugin that ships this one along with the rest of its 11 skills, 36 commands, 10 agents, 1 hook.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/glossary/github.svg)](https://agentmods.dev/commands/abhinavbwj/aec-scholar/glossary)
Your own site
<a href="https://agentmods.dev/commands/abhinavbwj/aec-scholar/glossary"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/glossary/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

Your own site · 80×15
<a href="https://agentmods.dev/commands/abhinavbwj/aec-scholar/glossary"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/glossary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 383 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.00017 $0.00383
Opus 5 $0.00009 $0.00192
Sonnet 5 $0.00003 $0.00077
Haiku 4.5 $0.00002 $0.00038

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

Security

Grade A, and why

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

aec-scholar/commands/glossary.md · 29 lines

What it actually says

Build a glossary for: $ARGUMENTS

Use the aec-domain-expert agent and the aec-domains + aec-standards-codes skills.

  1. Collect the terms. If text is provided, extract the domain terms, acronyms and abbreviations used. If a topic is given, list the key concepts a reader needs defined.

  2. Define each precisely in canonical AEC terminology — concise, accurate, and disambiguated where the field is loose (e.g. distinguish digital twin vs digital shadow vs BIM; embodied vs operational carbon; verification vs validation; LOD meanings). Reference the governing standard where one exists (e.g. "per ISO 19650", "EN 15978 stages A1–A3").

  3. Expand acronyms on first definition (BIM, IFC, LCA, EPD, nZEB, SHM, DfMA, MCDM, SEM, etc.) and keep them consistent.

  4. Format as an alphabetical glossary table (Term | Definition | Standard/Note), suitable for a thesis front-matter glossary or a paper's nomenclature section. For LaTeX users, offer a glossaries-package version.

Keep definitions faithful to established usage; flag any term whose meaning is contested in the literature and give the competing senses rather than picking one silently. Don't invent a definition for a term you can't ground — say it needs a source.

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 · 29 lines · 17 tokens per session scan A 12ef3bb0f621

Subscribe to this mod's changes

glossary is a command published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 383 once invoked, about $0.0001 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.