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 sageox/ox --skill ox-cli-consultgit clone --depth 1 https://github.com/sageox/oxWrote 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/sageox/ox/ox-cli-consult)<a href="https://agentmods.dev/skills/sageox/ox/ox-cli-consult"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-consult/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/sageox/ox/ox-cli-consult"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-consult.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.00140 | $0.00430 |
| Opus 5 | $0.00070 | $0.00215 |
| Sonnet 5 | $0.00028 | $0.00086 |
| Haiku 4.5 | $0.00014 | $0.00043 |
Grade A, and why
ox-cli-consult 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ox-consult — 88% identical, 2 lines differ
What it actually says
Use when
The user's message carries a consult cue — STOP and search before reasoning:
- References recent or specific work: "I just pushed...", "this request", "did X fix Y?", "is the alert gone now?"
- Touches a prior decision, a prod anomaly, or a metric/cost change — anything with a before/after.
Route the cue
The authoritative cue→corpus routing (recency vs conceptual vs code-provenance, with the
exact commands) lives in the <consult-first> block of your ox agent prime output —
follow it from there rather than from this file. If it is not in context (session not
primed), run ox agent prime first, then route.
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.
- 3d ago First seen · 35 lines · 140 tokens per session scan A e11d2fd4cebb
ox-cli-consult is a skill published in the GitHub repository sageox/ox (53 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 430 once invoked, about $0.0007 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-09-08.
Other skills, from other repositories
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
context-degradation
Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash.
context-compression
Design and evaluate compression strategies for long-running sessions.
context-optimization
Apply compaction, masking, and caching strategies.
archive
Archive or backfill compact records of completed activities.
maintaining-context
Use at the start of any substantial task and whenever you make a non-obvious decision or learn a reusable fact — keeps .yoke/context/ (PROJECT, DECISIONS, KNOWLEDGE) the durable source of truth so fresh-context work never drifts.