Borrowing it
Nothing to install: this file belongs to walm00/business-context-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/walm00/business-context-os/main/.claude/skills/context-audit/SKILL.mdgit clone --depth 1 https://github.com/walm00/business-context-osWrote 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/walm00/business-context-os/context-audit)<a href="https://agentmods.dev/skills/walm00/business-context-os/context-audit"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/context-audit.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.00115 | $0.02483 |
| Opus 5 | $0.00057 | $0.01241 |
| Sonnet 5 | $0.00023 | $0.00497 |
| Haiku 4.5 | $0.00012 | $0.00248 |
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 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.
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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Audit
Purpose
This skill IS:
- Auditing context data points for CLEAR compliance
- Finding duplication and ownership conflicts across data points
- Identifying boundary violations between context areas
- Enforcing consistency in naming, format, and structure
- Providing prioritized findings with improvement recommendations
This skill IS NOT:
- Making changes to context (audit only -- findings guide manual fixes)
- A fix-it tool (this finds problems, you fix them based on findings)
- Checking markdown syntax (use doc-lint for that)
- Planning new work (use clear-planner for that)
Instructions
Step 1: Define Audit Scope
Pre-read (cheap, do this first): if docs/document-index.md exists, read it before asking the scope question. It gives you the canonical inventory of active data points by cluster, ownership, and last-updated date — enough to suggest a smart default scope (e.g., "you have 14 data points across 3 clusters; 4 haven't been touched in 90+ days — audit those?") instead of asking blind. If absent, fall back to the question below directly.
If not specified, use the AskUserQuestion tool:
- Question: "What should I audit?"
- Options:
- Specific area (e.g., competitive intelligence data points)
- Full architecture (all active data points — comprehensive)
- Recent changes (only docs modified recently)
- Cross-cutting concern (e.g., all pricing-related data points across clusters)
Step 2: Gather and Check Metadata
Context window strategy: For scopes with 20+ documents, delegate the metadata scanning to an explore agent. Keep the main window for CLEAR analysis (Step 3).
# For large scopes:
Agent (Explore): "Read all .md files in [scope]. Skip dot-prefixed files
(.session-diary.md, .wake-up-context.md, .onboarding-checklist.md) — these are
conventions, not managed data points. For each remaining file, extract YAML
frontmatter and check: all 7 required fields present? status valid? last-updated
within 90 days (180 days for _planned/)? Return a validation table."
What ships with it
1 file 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.
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 · 266 lines · 115 tokens per session scan A 13d000cf993d
context-audit is a skill published in the GitHub repository walm00/business-context-os (21 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 2,483 once invoked, about $0.0006 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-30.
Other skills, from other repositories
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.