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/ngocsangyem/meowkit/context-auditnpx skills add ngocsangyem/MeowKit --skill context-auditgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/context-audit)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/context-audit"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/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.00108 | $0.01450 |
| Opus 5 | $0.00054 | $0.00725 |
| Sonnet 5 | $0.00022 | $0.00290 |
| Haiku 4.5 | $0.00011 | $0.00145 |
Grade A, and why
mk: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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mk:context-audit — Context Window Structural Audit
Read-only audit of .claude/ structural overhead. Surfaces what is loaded into
every host-runtime session and how much of the context window it consumes,
then recommends the highest-leverage trims.
Complementary lens: mewkit inventory --substrate shows the same artifact set
grouped by the responsibility each serves (covered / partial / missing), so a trim
can be checked against responsibility coverage before removing an artifact. The
per-phase read budget that bounds what an audit-driven session should load lives in
rules/context-budget-rules.md.
When to Use
Three concrete triggers:
- Pre-add capacity check — before adding a new agent, skill, or rule file, confirm the project is below the 25% structural-overhead threshold.
- Post-degradation diagnostic — when sessions feel slow, off-topic, or over-compacted, audit to see if structural overhead has grown past 10%.
- Periodic health audit — quarterly or on model upgrades, confirm
the always-on bundle still pays its keep (paired with the dead-weight audit
in
harness-rules.mdRule 7).
Context vs Cost (Boundary)
| Concern | Mechanism | Unit |
|---|---|---|
| Monetary cost | /mk:budget + ../autobuild/scripts/budget-tracker.sh |
USD |
| Window utilization (this skill) | /mk:context-audit + scripts/inventory-context.sh |
tokens / % |
The three concerns are deliberately separate. This skill measures only what is statically loaded into every session — the always-on bundle. Conversation history, tool output, and active edits live elsewhere.
Workflow
The slash command runs the pipeline:
SCAN_ROOT="${1:-$PWD}"
bash .claude/skills/context-audit/scripts/inventory-context.sh "$SCAN_ROOT" \
| bash .claude/skills/context-audit/scripts/estimate-tokens.sh \
| bash .claude/skills/context-audit/scripts/format-audit-report.sh
What ships with it
6 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.
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 · 154 lines · 108 tokens per session scan A 805fa304b84e
mk:context-audit is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 1,450 once invoked, about $0.0005 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
pw-admin-ui
Use when designing, structuring, or rendering HTML for ProcessWire Admin interfaces, custom Process modules, or Inputfields.
pw-module-development
Use when building, structuring, or refactoring native backend modules for ProcessWire using PHP 8.4 and strict typing.
pw-custom-page-classes
Use when extending ProcessWire's base Page class to create specialized, strongly-typed custom classes representing specific templates.
pw-docs-architect
Use when creating or updating module documentation, package READMEs, architecture guides, or CLI command references for ProcessWire projects.
pw-expert
Use when working with Laravel Prompts/Symfony Console command patterns, or when determining the correct, context-safe way to access ProcessWire API variables like $page, $pages, or $user.
pw-module-fieldtype-inputfield
Use when building custom database fieldtypes and their corresponding interface inputfields in ProcessWire.