setup

An interactive setup tool for configuring ContextGuard, a project-local collection of token-saving and context-management settings for Claude Code.

In plain words
What is it for?
Use it to check setup health, preview configuration changes, enable local protections for bulky reads and command output, add status information, and configure related defaults.
Why use it?
It lets you inspect available safeguards and apply selected settings without manually editing configuration files or memorizing commands.

Skill for Claude CodeCodex

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 skills/ictechgy/context-guard/setup
Any agent
npx skills add ictechgy/context-guard --skill setup
Clone the repo
git clone --depth 1 https://github.com/ictechgy/context-guard

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 425 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00035 $0.00425
Opus 5 $0.00017 $0.00212
Sonnet 5 $0.00007 $0.00085
Haiku 4.5 $0.00003 $0.00042

Measured yesterday against content hash deb6f90cf540, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

setup scanned grade B with 1 finding 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 yesterday.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- Do not modify global `~/.claude/settings.json`.
plugins/context-guard/skills/setup/SKILL.md · 44 lines

What it actually says

ContextGuard Setup

Goal: help the user configure this plugin without memorizing helper commands.

Default flow:

  1. Run a read-only health check and plan first:
context-guard-setup --verify
context-guard-setup --plan
  1. Explain the options briefly:
    • deny bulky/sensitive reads,
    • token/cost statusline,
    • Bash trim + grep/diff sanitizer hook,
    • large Read guard,
    • failed-attempt nudge for repeated Bash failures,
    • missing model/effort defaults.
  2. If the user wants the recommended project-local setup, run:
context-guard-setup --yes
  1. Treat the post-apply context-guard-diet scan summary emitted by setup as the default remaining-gap check; run context-guard-diet scan . separately only when the user wants the full report.
  2. For automation that must skip the post-apply scan summary, run context-guard-setup --no-diet-scan --yes.
  3. If they want extra token reduction beyond setup, prefer local artifact escrow, symbol reads, and semantic digests rather than external model offload.

Safety:

  • Do not modify global ~/.claude/settings.json.
  • Prefer project-local .claude/settings.json.
  • context-guard-setup --verify is a local read-only health check and never applies settings.
  • Setup's post-apply scan is local, read-only, and prints a summary only; it does not mutate settings.
  • Setup should use packaged/check-out helper paths by default; only pass --allow-path-helper-fallback when the user explicitly trusts a PATH-installed ContextGuard helper set.
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. yesterday First seen · 44 lines · 35 tokens per session scan B deb6f90cf540

Subscribe to this mod's changes

setup is a skill published in the GitHub repository ictechgy/context-guard (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 425 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories