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 commands/shakestzd/contextune/ctx-configuregit clone --depth 1 https://github.com/shakestzd/contextuneWrote 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/commands/shakestzd/contextune/ctx-configure)<a href="https://agentmods.dev/commands/shakestzd/contextune/ctx-configure"><img src="https://agentmods.dev/badge/commands/shakestzd/contextune/ctx-configure.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 | $0.00022 | $0.02226 |
| Opus 5 | $0.00011 | $0.01113 |
| Sonnet 5 | $0.00004 | $0.00445 |
| Haiku 4.5 | $0.00002 | $0.00223 |
Grade B, and why
ctx:configure 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
if grep -q '"slashsense@Contextune".*true' ~/.claude/settings.json 2>/dev/null; then How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contextune Interactive Configuration
Interactive setup for Contextune features with guided prompts.
What this configures:
- ✨ Extraction-optimized output style (automatic documentation)
- 🎨 Status bar integration (optional)
- 📝 CLAUDE.md integration (optional)
Run /ctx:configure and Claude will guide you through interactive prompts.
Quick Start
/ctx:configure
Claude will detect your current setup and present interactive options via dialog prompts.
Interactive Flows
Flow 1: First-Time Setup (Complete Setup in One Command)
When you run /ctx:configure and nothing is installed, Claude guides you through:
Step 1: "Would you like to install the extraction-optimized output style?"
- Install - Enable automatic documentation extraction
- Skip - Continue without
Step 2 (if Install): "Where should the output style be installed?"
- This project - Install to
.claude/output-styles/(git-trackable, team can share) - All projects - Install to
~/.claude/output-styles/(available everywhere)
Step 3: "Would you like to add Contextune to your status bar?"
- Yes - Show Contextune commands in status bar (zero token cost)
- No - Skip status bar integration
Result: Complete setup with your preferred configuration ✅
Flow 2: Manage Existing Installation
If customizations are already installed, Claude offers:
"Manage Contextune configuration"
Current installation displayed (e.g., "Output style: user-level, Status line: ✅")
- Activate style - Make extraction-optimized active for this session
- Reinstall - Change installation scope (user ↔ project)
- Uninstall - Remove all customizations
- Keep as-is - No changes
Flow 3: Uninstall (Clean Removal)
If you choose to uninstall, Claude shows:
⚠️ Important Warning:
Before disabling the Contextune plugin (
/plugin disable contextune), run this uninstall process FIRST.The plugin's hooks won't be available after disabling, so remove customizations while the plugin is still active.
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.
- 4d ago First seen · 332 lines · 22 tokens per session scan B b182d815f3da
ctx:configure is a command published in the GitHub repository shakestzd/contextune (5 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 2,226 once invoked, about $0.0001 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.
Other commands, from other repositories
ccboard-install
Install or update ccboard.
agy-setup
Print the plugin's install path and the command to install agy-delegate's launcher wrappers (agy-bridge + gemini shim).
security-review
CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제).
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
plan-start
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/plan-pipeline/start/SKILL.md.
catchup
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/catchup/SKILL.md.