What is extract-spec?

A command that reads an APEXlang page or component and writes a plain-language specification. The specification describes its structure, data sources, interactions, navigation, and visible business rules.

Use it to document an existing page or component and save the result as a Markdown file under specs/.

It turns hard-to-read application metadata into documentation that developers can review and correct. This makes it easier to understand or rebuild a page without studying the original files.

extract-spec — Command for Claude Code by maxime-tremblay

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/maxime-tremblay/APEXLang-Project-Template

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/maxime-tremblay/apexlang-project-template/extract-spec/github.svg)](https://agentmods.dev/commands/maxime-tremblay/apexlang-project-template/extract-spec)

Your own site

<a href="https://agentmods.dev/commands/maxime-tremblay/apexlang-project-template/extract-spec"><img src="https://agentmods.dev/badge/commands/maxime-tremblay/apexlang-project-template/extract-spec/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/maxime-tremblay/apexlang-project-template/extract-spec"><img src="https://agentmods.dev/badge/commands/maxime-tremblay/apexlang-project-template/extract-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 227 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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00227
Opus 5.5	$0.00007	$0.00091
Sonnet 5.5	$0.00004	$0.00045
Haiku 4.5	$0.00002	$0.00023

Measured 2mo ago against content hash 93eb09cf08fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

extract-spec 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 2mo 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.

.claude/commands/extract-spec.md · 22 lines

What it actually says

Analyse the APEXLang files for the page or component specified by the developer and produce a clean, human-readable spec.

Steps:

Ask the developer which page or component to analyse if not already specified
Locate the relevant .apx files in app/
Read the files and identify: page structure, regions, items, processes, dynamic actions, navigation
Produce a spec document in plain language covering:
- Purpose of the page or component
- Data sources used (tables, views, packages)
- User interactions and expected behaviour
- Business rules visible in the metadata
- Any naming or structural conventions observed
Save the spec to specs/{page-alias}-spec.md
Ask the developer to review and correct anything before using the spec to make changes

The spec should be clear enough that another developer — or this AI in a future session — could rebuild the page from it without needing to read the raw APEXLang files.

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.

2mo ago First seen · 22 lines · 18 tokens per session scan A 93eb09cf08fc

Subscribe to this mod's changes

extract-spec is a command published in the GitHub repository maxime-tremblay/APEXLang-Project-Template (2 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 227 once invoked, about $0.0001 per session on Opus 5.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.

Planning

extract-spec next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
extract-specmaxime-tremblay/APEXLang-Project-Template	Command	2	5mo ago	MIT	A	18	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
speckit.bug.testgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code