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 littlebearapps/contextdocs --skill context-guardgit clone --depth 1 https://github.com/littlebearapps/contextdocsWrote 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/littlebearapps/contextdocs/context-guard)<a href="https://agentmods.dev/skills/littlebearapps/contextdocs/context-guard"><img src="https://agentmods.dev/badge/skills/littlebearapps/contextdocs/context-guard/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/littlebearapps/contextdocs/context-guard"><img src="https://agentmods.dev/badge/skills/littlebearapps/contextdocs/context-guard.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.00066 | $0.01926 |
| Opus 5.5 | $0.00026 | $0.00770 |
| Sonnet 5.5 | $0.00013 | $0.00385 |
| Haiku 4.5 | $0.00007 | $0.00193 |
Grade A, and why
context-guard 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 1mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Guard
What It Does
Hooks and a quality rule to keep AI context files in sync with the codebase. Prevents content filter errors on standard OSS files. Two-tier enforcement for context doc freshness.
Primary platform: Claude Code (full automation, 12 hook events). Other platforms with hook support — Gemini CLI (11 events), Copilot (8, preview), Cursor (4+), Cline (3) — can use adapted hooks from platforms/ packages (coming soon). For platforms without hooks (Codex CLI, OpenCode, Windsurf), use bin/context-verify.sh as a manual or CI-based alternative.
Enforcement Tiers
| Tier | Name | Mechanism | Behaviour |
|---|---|---|---|
| 1 | Nudge | Stop hook | Advisory — suggests updating context docs before session ends |
| 2 | Guard | PreToolUse on git commit |
Blocking — prevents commits when structural files staged without context updates (exit 2) |
Default: Tier 1 only. Add Tier 2 with install strict.
Components
content-filter-guard.sh (PreToolUse → Write)
- HIGH-risk (CODE_OF_CONDUCT.md, LICENSE, SECURITY.md): blocks write, returns fetch commands for canonical URL
- MEDIUM-risk (CHANGELOG.md, CONTRIBUTING.md): allows write, advises chunked writing
- All other files: passes through silently
context-structural-change.sh (PostToolUse → Write|Edit)
Fires after creating/editing structural files. Reminds which context files may need updating:
commands/*.md,.claude/skills/*/SKILL.md,.agents/skills/*/SKILL.md→ updateAGENTS.mdfirst, thenCLAUDE.md,llms.txt, and any affected bridge files.claude/agents/*.md,.agents/agents/*.md→AGENTS.md,llms.txt.claude/rules/*.md→AGENTS.mdandCLAUDE.mdif rule references changed- Config files (
package.json,pyproject.toml, etc.) → updateAGENTS.mdfirst, then only the bridge files with tool-specific command/tooling notes
If your repository uses the .agents/ layout instead of .claude/, apply the same AGENTS-first update order to the equivalent skill and agent paths above.
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.
- 1mo ago First seen · 138 lines · 66 tokens per session scan A b12b8ff9dea7
context-guard is a skill published in the GitHub repository littlebearapps/contextdocs (5 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 1,926 once invoked, about $0.0003 per session on Opus 5.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
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.
session-handoff
Documents the current Claude Code session by writing what changed, what broke, how problems were solved, and what's next into DECISIONS.md, CONTEXT.md, and CLAUDE.md. Then commits everything to git. Use this skill when the user says they are done, wrapping up, finishing, handing off, ending the session, switching…
team-collaboration-issue
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an.
douchebag-commit
Generate commit messages with loud gym-bro-chad voice in the body. Subject line stays Conventional-Commits compliant, clean, and profanity-free. Triggered by /douchebag-commit.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.