Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add racecraft-lab/racecraft-plugins-public/plugin install speckit-proWrote 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/racecraft-lab/racecraft-plugins-public/ubiquitous-language)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/ubiquitous-language"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/ubiquitous-language/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/racecraft-lab/racecraft-plugins-public/ubiquitous-language"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/ubiquitous-language.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.00000 | $0.01476 |
| Opus 5.5 | $0.00000 | $0.00590 |
| Sonnet 5.5 | $0.00000 | $0.00295 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
ubiquitous-language 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 16d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ubiquitous Language
Write and maintain docs/ai/specs/ubiquitous-language.md: one table of the
domain terms this repository uses, what each means here, and the code
identifiers that carry it. Grill Me and PRD authoring read it when present, so
a term is pinned once and reused instead of re-derived in every interview.
In Codex, use $skill-name syntax for plugin skills.
Ground recommendations
Inspect the tools and skills actually available. Follow the shared
capability-discovery and grounding contracts.
capability-discovery and grounding contracts.
A term's meaning comes from the code and documents that use it; disclose uncertainty and do not invent a definition.
Workflow
- Read what exists. If
docs/ai/specs/ubiquitous-language.mdexists, read it first and treat its rows as settled unless the user reopens one. Read.specify/memory/constitution.md, the technical roadmaps underdocs/ai/specs/, and any PRD underdocs/for terms already in use. - Scan the repository. Collect candidate terms from module and package
names, exported classes and functions, database tables and columns, API
routes, and README or docs headings. Group names that split the same
concept (
Invoice,bill,statement) and names that overload one word for two concepts. - Propose the table. For each term, write one row: the term, its meaning in this repository in one sentence, and the identifiers that carry it. Where the codebase disagrees with itself, propose one term and list the other spellings under Identifiers so the lint maps them. Ask the user about
a genuinely ambiguous term with AskUserQuestion, one term at a time, with
your recommendation first; do not ask about terms the evidence settles.
a genuinely ambiguous term one at a time, recommendation first: prefer
request_user_input; in an already active user chat with no picker, ask
the one question in free text. Never use this fallback in background, CI,
autopilot, or subagent execution. Do not ask about terms the evidence
settles.
- Write the document only after the user confirms the proposal. Keep the format exactly:
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.
- 16d ago Changed 6e1a7519358c
- 19d ago Changed · +34 lines · -114 tokens per session 21e4e6407ff4
- 20d ago Changed b666d7137018
- 1mo ago First seen · 70 lines · 114 tokens per session scan A 2a5af9d9e583
ubiquitous-language is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,476 tokens. 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-09-10.
Other skills, from other repositories
build-executor
Execute an active direct request or approved planned change. Native continuous implementation is the default; existing legacy changes retain their recorded contract obligations.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.
contract-builder
Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
need-explorer
Clarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.