context-guard

A command that has moved its context-file freshness checks to the ContextDocs plugin. Context files are instruction or reference files an AI coding agent reads while working.

In plain words
What is it for?
Use ContextDocs to install reminders or commit blocking for stale context files, remove those hooks, or check their status.
Why use it?
The command itself no longer provides the checks, so installing or using it alone will not set them up.

Command

Install

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.

agentmods
npx agentmods add commands/littlebearapps/pitchdocs/context-guard
Clone the repo
git clone --depth 1 https://github.com/littlebearapps/pitchdocs
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 207 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00207
Opus 5 $0.00006 $0.00103
Sonnet 5 $0.00003 $0.00041
Haiku 4.5 $0.00001 $0.00021

Measured 2d ago against content hash 8de200d6d626, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/context-guard.md · 27 lines

What it actually says

/context-guard — Moved to ContextDocs

Context Guard hooks for AI context file freshness have moved to the ContextDocs plugin.

Install ContextDocs

/plugin install contextdocs@lba-plugins

Then Use

/contextdocs:context-guard install          # Tier 1 — Nudge (session-end reminder)
/contextdocs:context-guard install strict   # Tier 1 + Tier 2 (commit blocking)
/contextdocs:context-guard uninstall        # Remove all hooks
/contextdocs:context-guard status           # Check installation state and drift

Context Guard includes the same two-tier enforcement, content filter protection, and Untether compatibility — now in its own focused plugin.

Changes

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.

  1. 2d ago First seen · 27 lines · 13 tokens per session scan A 8de200d6d626

Subscribe to this mod's changes

context-guard is a command published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 207 once invoked, about $0.0001 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.