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 skills add metraton/gaia --skill brief-specgit clone --depth 1 https://github.com/metraton/gaiaWrote 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/metraton/gaia/brief-spec)<a href="https://agentmods.dev/skills/metraton/gaia/brief-spec"><img src="https://agentmods.dev/badge/skills/metraton/gaia/brief-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.
<a href="https://agentmods.dev/skills/metraton/gaia/brief-spec"><img src="https://agentmods.dev/badge/skills/metraton/gaia/brief-spec.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.00019 | $0.03554 |
| Opus 5 | $0.00010 | $0.01777 |
| Sonnet 5 | $0.00004 | $0.00711 |
| Haiku 4.5 | $0.00002 | $0.00355 |
Grade A, and why
brief-spec scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
query: "curl -s http://localhost:3000/metrics | grep http_p95" How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brief Spec
Conversational brief creation. The orchestrator loads this inline to co-create a brief with the user before dispatching to gaia-planner. The brief you write here is the contract you will audit the plan against: you own the resulting plan -- its tasks and its acceptance criteria -- and the planner produces it for you to check, not to approve on your behalf.
DB is the source of truth (read this first)
Briefs live in the Gaia substrate database (~/.gaia/gaia.db). They are
created and mutated through the gaia brief CLI -- never by writing files
on disk. The DB row IS the brief: there is no brief.md, no
<status>_<slug>/ directory, no frontmatter on disk. When in doubt, there
is no file to write -- there is a CLI command to run.
Execution follows authority. The orchestrator co-creates the brief and may
use its trusted Gaia CLI lane for bounded reads and user-confirmed
new/headless edit/set-status/AC writes. gaia-operator remains the
alternative for batching or operational separation. Destructive deletion is
outside the direct lane. The orchestrator owns the questions, confirmation,
and content whichever executor carries the command.
If you find code, docs, or skills that still describe a filesystem layout
under .claude/project-context/briefs/, that is legacy: flag it in
cross_layer_impacts -- do not edit it as a side effect of a brief task.
Cuando llegas aquí
El orquestador cargó esta skill porque la conversación entró en Cerrar: el usuario y él han acordado varias cosas y es momento de materializarlas. No estás aquí porque la petición superó un umbral de tamaño. Estás aquí porque hay acuerdos que capturar.
Tu trabajo:
- Resumir los acuerdos que ya emergieron en la conversación previa -- no re-descubrirlos desde cero.
- Preguntar sólo lo que falte para convertir los acuerdos en AC reproducibles (evidence types, surface type).
- Materializar el brief en la DB con
gaia brief new --headless, y presentarlo al usuario para validar.
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.
- 8d ago First seen · 370 lines · 19 tokens per session scan A e3a6f2525854
brief-spec is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 3,554 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
review-team
A multi-reviewer code review process that checks a change from several specialist viewpoints and combines the results into one report. It can cover bugs, security, tests, dependencies, frontend behavior, and continuous-integration workflows.
ultra
Fans the work out as a fleet of parallel Grok and Codex agents billed to their own subscriptions, then synthesizes one result. The peer engine equivalent of ultracode, adding intensity without spending Claude quota on the fleet. Use it for genuinely broad goals, not only explicit asks for intensity.
grok-prompting
Brief writing guidance for composing self contained Grok briefs for coding, review, diagnosis, and second opinion tasks.
smoke
Runs a three probe live smoke wave after a plugin update and reports gate chain health before real work rides it.
codex-result-handling
Internal contract for returning Codex companion output without alteration.
shipwrights-loop
Drive multiple Jira tickets sequentially through the /shipwrights-epic pipeline. Auto-picks the next ticket, watches the PR until merged, transitions Jira to shipped, repeats. Resumable across Claude Code sessions via .shipwrights/loop-state.json. Invoked as /shipwrights-loop [N] | --status | --abort.