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 opencue/cuecards --skill vc-audit-contextgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/vc-audit-context)<a href="https://agentmods.dev/skills/opencue/cuecards/vc-audit-context"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-audit-context.svg" alt="Measured on agentmods" 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.00039 | $0.00613 |
| Opus 5 | $0.00019 | $0.00307 |
| Sonnet 5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
vc:audit-context 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Context
Use this skill to verify that Flowser's durable context layer is discoverable and organized.
Optional input: a context group, agent, skill, or folder scope to prioritize during the audit.
Workflow
- Read
process/context/all-context.mdfor the context routing protocol. - Read
references/audit-context.mdfor the full audit process. - Run the context discovery validator:
node .Codex/skills/vc-audit-context/scripts/validate-context-discovery.mjs - Run the shared skill routing coverage validator:
node .Codex/skills/vc-audit-context/scripts/validate-skill-routing.mjs - Run the skill cross-reference validator:
node .Codex/skills/vc-audit-context/scripts/validate-skill-cross-refs.mjs - Run the skill dependency/confusable analysis:
node .Codex/skills/vc-audit-context/scripts/validate-skill-dependencies.mjs node .Codex/skills/vc-audit-context/scripts/validate-confusable-skills.mjs - Regenerate or check the machine-readable skill catalog:
node .Codex/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --write node .Codex/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --check - If any script reports failures, inspect the referenced files and patch the smallest relevant surface.
- Re-run the failed validators until they pass.
For agent/skill harness validation (agent parity, skill frontmatter, README.md sync, protocol wiring), use the audit-vc skill.
Rules
- Treat
.Codex/skills/as canonical;.agents/skills/is the Codex discovery symlink. - Treat
.Codex/skills/vc-audit-context/references/skill-routing-policy.jsonas the explicit allowlist for intentionally non-routed shared skills. - Do not move large context files without updating
process/context/all-context.md. - Do not delete compatibility wrappers unless no current reference points to them.
- Keep context groups durable-domain based, not one group per temporary feature.
- When updating agents, mirror Codex markdown and Codex TOML surfaces together.
- Treat validator warnings as audit findings unless the user asks for a strict cleanup.
- Prefer validator-backed routing truth over adding more soft prose.
- Treat
process/context/generated-skills-catalog.jsonas the machine-readable catalog owned byaudit-context.
What ships with it
9 files 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.
- references/audit-context.md 5.3 KB
- references/skill-routing-policy.json 257 B
- scripts/generate-skills-catalog.mjs 2.0 KB runs code
- scripts/shared-skill-utils.mjs 5.0 KB runs code
- scripts/validate-confusable-skills.mjs 1.3 KB runs code
- scripts/validate-context-discovery.mjs 11 KB runs code
- scripts/validate-skill-cross-refs.mjs 820 B runs code
- scripts/validate-skill-dependencies.mjs 1.2 KB runs code
- scripts/validate-skill-routing.mjs 3.4 KB runs code
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 · 58 lines · 39 tokens per session scan A 928b239179b6
vc:audit-context is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 613 once invoked, about $0.0002 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-03.
Other skills, from other repositories
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.