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 agentmods add skills/zts0hg/codexspec/codexspec-commit-stagednpx skills add Zts0hg/codexspec --skill codexspec-commit-stagedgit clone --depth 1 https://github.com/Zts0hg/codexspecWhat 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 | $0.00026 | $0.01626 |
| Opus 5 | $0.00013 | $0.00813 |
| Sonnet 5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
codexspec:commit-staged 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution Compliance (MANDATORY)
Before generating commit messages:
- Check for Constitution File: Look for
.codexspec/memory/constitution.md - If Constitution Exists:
- Load and read relevant principles (especially coding standards, commit conventions)
- Ensure commit message style aligns with constitutional guidelines
- Verify that the changes being committed don't violate any principles
- If No Constitution Exists: Proceed with default Conventional Commits format
Configuration Check
IMPORTANT: Before proceeding, check if the project configuration exists.
Execution Steps
-
Check Configuration File
- Check if
.codexspec/config.ymlexists - This is a simple file existence check, no parsing needed at this stage
- Check if
-
If Configuration Does NOT Exist
-
Display a one-time prompt:
💡 Project language is not configured. Run `$codexspec:config` to create a configuration file. -
Use default values for current session:
language.output: "en"language.commit: "en"language.templates: "en"
-
Continue with command execution normally
-
-
If Configuration Exists
- Proceed to
## Language Preferencesection - Read configuration and apply language settings as before
- Proceed to
-
Session State (Implicit)
- The prompt is shown only once per conversation session
- Claude's conversation context naturally maintains this state
- No additional mechanism needed
Language Preference
IMPORTANT: Before generating commit messages, read the project's language configuration from .codexspec/config.yml.
Commit message language priority:
- If
language.commitis set, use that language for the commit message description - Otherwise, use
language.outputas fallback - If neither is configured, default to English
Note:
- The commit type (feat, fix, docs, etc.) and scope should always remain in English
- Only the description part should use the configured language
- Technical terms (e.g., API, JWT, OAuth) may remain in English when appropriate
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.
- 2d ago First seen · 168 lines · 26 tokens per session scan A bbb17cbbb109
codexspec:commit-staged is a skill published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 1,626 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-31.
Other skills, from other repositories
airflow-translations
Add or update translations for the Apache Airflow UI. Guides through setting up locales, scaffolding translation files, translating with locale-specific guidelines, and validating results. Use when working with i18n tasks in airflow-core/src/airflow/ui/public/i18n/locales/.
intlayer-angular
Integrates Intlayer internationalization with Angular applications. Use when the user asks to "setup Angular i18n", create a new translated component, use the "useIntlayer" composable, or configure providers.
intlayer-next-js
Integrates Intlayer internationalization with Next.js App Router and Pages Router. Use when the user asks to "setup Next.js i18n", use "useIntlayer" in Server Components, or handle client-side translations in Next.js.
intlayer-react
Integrates Intlayer internationalization with React component. Use when the user asks to "setup React i18n", create a new translated component, use the "useIntlayer" hook, or configure providers.
intlayer-cli
Manages Intlayer dictionaries and configuration via the Command Line Interface. Use when the user asks to "audit translations", "build dictionaries", "sync content", or run "intlayer" commands.
intlayer-preact
Integrates Intlayer internationalization with Preact applications. Use when the user asks to "setup Preact i18n", create a new translated component, use the "useIntlayer" hook in Preact, or configure providers.