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/greglas75/zuvo/context-auditnpx skills add greglas75/zuvo --skill context-auditgit clone --depth 1 https://github.com/greglas75/zuvoWhat 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.00054 | $0.03016 |
| Opus 5 | $0.00027 | $0.01508 |
| Sonnet 5 | $0.00011 | $0.00603 |
| Haiku 4.5 | $0.00005 | $0.00302 |
Grade A, and why
context-audit 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:context-audit — Context Health Monitor
Tracks what fills your context window over time and flags waste. Two data sources:
- Auto-collected —
~/.zuvo/runs.logfield 12 (name:bytespairs, populated bytrack-includes.shhook on every Read) - Manual —
/contextoutput (optional, for full system-level audit)
Argument Parsing
| Flag | Effect |
|---|---|
--full |
Full audit: requires /context data. Audits MCP, CLAUDE.md, settings, permissions |
--baseline |
Save current state as baseline for future delta comparisons |
--since N |
Show trend for last N days (default: 7) |
| (no flags) | Trend mode: analyze context-metrics.log, show include loading patterns |
Mandatory File Loading
Read these files:
CORE FILES LOADED:
1. ../../shared/includes/run-logger.md -- READ
2. ../../shared/includes/retrospective.md -- READ
Phase 0: Collect Data
Metrics data (from runs.log)
Read ~/.zuvo/runs.log — the single source of truth for all skill run data:
RUNS_LOG="$HOME/.zuvo/runs.log"
Filter entries that have INCLUDES data (field 12 contains :). These are v3+ entries with name:bytes format.
# Extract v3 entries (field 12 has name:bytes pairs)
awk -F'\t' 'NF>=12 && $12 ~ /:/' "$RUNS_LOG"
If fewer than 3 entries with INCLUDES data: print "Not enough data yet. Run a few zuvo skills first — the track-includes.sh hook captures include sizes automatically." and exit.
Parse field 12 as name:bytes|name:bytes pairs. Calculate per-include sizes and cumulative costs directly from this field. No separate metrics file needed.
/context data (--full mode only)
Check conversation history for /context output. If not found:
"Run /context in this session and let me know when you're done. I need the token breakdown to audit your full setup."
STOP HERE in --full mode. Do not proceed until the user provides /context data.
In default trend mode: skip this step entirely, proceed with metrics data.
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 · 340 lines · 54 tokens per session scan A 594e0a653d43
context-audit is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 3,016 once invoked, about $0.0003 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
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
ring:writing-plans
Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…
ring:writing-skills
Writing or editing a Ring skill: SKILL.md structure, frontmatter and Agent-Search-Optimization rules, token-efficiency targets, and bulletproofing (Iron Law, rationalization tables, Red Flags) so discipline-enforcing skills resist excuses. Use when creating or revising a skill. Delegates pressure-testing to…