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 tmusser/ai-engineering-skills --skill context-checkgit clone --depth 1 https://github.com/tmusser/ai-engineering-skillsWrote 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/tmusser/ai-engineering-skills/context-check)<a href="https://agentmods.dev/skills/tmusser/ai-engineering-skills/context-check"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/context-check/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/tmusser/ai-engineering-skills/context-check"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/context-check.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.00034 | $0.00639 |
| Opus 5 | $0.00017 | $0.00319 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
context-check 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Check
Purpose
Keep sessions cheap, bounded, and durable. Detect distortion early and recommend minimal correction.
When to use
Passive guardrail. Speak only on medium/high risk (or when explicitly invoked).
Low risk: stay silent unless explicitly invoked. If explicitly invoked on low risk, output one line: CONTEXT RISK: low — continue.
Trigger on repeated facts, scope/hypothesis changes, multiple debug hypotheses, handoff pressure, or active modes that may need to persist.
Inputs
- Current conversation
- Durable state files if present
- Current task, phase, loop, and active modes if known
- Current debugging hypothesis if debugging
- Where to record the result when the check is medium/high risk
Workflow
- Scan for risk signals (repeated premises, history restatement, scope drift, hypothesis sprawl, weak durable state, active-mode loss).
- Assign risk: low / medium / high.
- Recommend exactly one best move. For medium/high risk, prefer: scope-freeze | update durable state | handoff | diagnose-loop | restart. Use
continueonly for explicit low-risk checks. - Record where to persist the result when the risk is medium/high:
RECORD IN: HANDOFF.md | VERIFY.md | SPEC.md | none. - On medium/high risk, output the structured block. Recommend restart only when context is actively corrupting decisions.
Output format (medium/high only):
CONTEXT RISK: medium
TRIGGER: repeated premise repair on X
BEST MOVE: handoff | scope-freeze | update PLAN.md | etc.
FREEZE NOW: [key facts/decisions/modes/hypothesis]
NEXT ACTION: ...
RECORD IN: HANDOFF.md | VERIFY.md | SPEC.md | none
Keep FREEZE NOW limited to facts, decisions, assumptions, IDs, files, tests, active modes, current hypothesis, and next verification that must survive.
Outputs
- Concise risk assessment
- One recommended action
- Minimal freeze list when needed
Success looks like
- Low risk → no output (unless explicitly invoked), work continues cleanly.
- Medium risk → quick state update prevents drift.
- High risk → handoff or restart before more damage.
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 · 84 lines · 34 tokens per session scan A 83557af21f1b
context-check is a skill published in the GitHub repository tmusser/ai-engineering-skills (4 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 639 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-08-31.
Other skills, from other repositories
awsl
Run Claude Code JavaScript Workflows through the awsl compatibility runtime. Use when an agent's current task or loaded Skill requires dispatching a Claude Code Workflow but the host cannot execute that Workflow natively, or when awsl workflow inspection, durable run state, resume, or provider diagnostics are needed.
dwi-all-in-one
Apply the relevant Dwi lenses together when several observed workflow problems co-occur. Select only the lenses the task needs, preserve a silent fast path for clear reversible work, and keep authority and evidence explicit. Prefer a focused module when one issue dominates.
dwi-arc
Structure genuinely multi-agent coding work into bounded cells with one writer per scope, explicit integration, and independent review. Use when several disjoint workstreams justify coordination. Do not use for small tasks, overlapping writers, speculative agent fleets, or process artifacts without demonstrated value.
dwi-bridge
Coordinate bounded work between native Claude and Codex workflows with explicit authority, scope, and evidence. Use for read-only consultation or explicitly authorized execution delegation. Do not create a new connector, share secrets, treat messages as authorization, or allow recursive delegation.
dwi-budget
Set and report practical token, context, time, tool-call, and coordination boundaries for coding-agent work. Use when resource use is unclear or needs a checkpoint. Do not invent measurements, monetary savings, cache benefit, or precision that the harness does not expose.
dwi-evidence
Label coding-agent claims by evidence status, preserve provenance and failures, and separate static, runtime, and human proof. Use before completion, comparison, promotion, or handoff. Do not upgrade observations into guarantees or fabricate missing measurements and approvals.