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 fast-queriesgit 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/fast-queries)<a href="https://agentmods.dev/skills/metraton/gaia/fast-queries"><img src="https://agentmods.dev/badge/skills/metraton/gaia/fast-queries/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/fast-queries"><img src="https://agentmods.dev/badge/skills/metraton/gaia/fast-queries.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.00020 | $0.00246 |
| Opus 5 | $0.00010 | $0.00123 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
fast-queries 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.
What it actually says
Fast Queries
Start with supplied evidence, not a fixed diagnostic script.
- Read the injected dispatch kernel (
# Your Contract: goal,project, yourcan_readmenu). Project context is NOT preloaded. - Pull what the goal needs from the persistent substrate, narrowly scoped.
The read vocabulary -- which verb opens which coordinate, what each returns,
and the workspace rule -- is in
agent-protocol/read-map.md. - Run the smallest authoritative read-only CLI query for the surfaced domain. Use native output/filter flags and one command per call.
- Record the query, result, and uncertainty in the contract checkpoint.
- Deep-dive only where the evidence identifies a gap or inconsistency.
Do not invoke helpers from .claude/; that tree is an installed/protected
surface, not Gaia source. Do not treat a broad health command's exit code as
proof of a specific desired state. If investigation forecasts mutation, switch
to investigation and collect predictable exact T3 commands before requesting
consent.
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.
- 9d ago First seen · 25 lines · 20 tokens per session scan A da9668afcaf5
fast-queries is a skill published in the GitHub repository metraton/gaia (3 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 246 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - reproduce and isolate before changing anything.
shipwrights-doctor
Diagnose .shipwrights.yml — schema validity, agent availability, command discoverability, source adapter connectivity, guard registration, lock service reachability, telemetry log writability. Read-only. Invoked as /shipwrights-doctor.
wave-execution-framework-v2
Use when executing multi-wave engineering work needing strict TDD, bug-capture/fix split, quality gates, and orchestrated teams with per-agent Opus-advisor / Sonnet-executor model routing.
stress-test
Adversarial plan stress-testing with POC code verification.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…