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.
git clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/context)<a href="https://agentmods.dev/commands/komluk/scaffolding/context"><img src="https://agentmods.dev/badge/commands/komluk/scaffolding/context/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/commands/komluk/scaffolding/context"><img src="https://agentmods.dev/badge/commands/komluk/scaffolding/context.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.00019 | $0.00436 |
| Opus 5.5 | $0.00008 | $0.00174 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
context 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.
What it actually says
/context Command
Analyze and optimize Claude Code's context configuration.
Usage
/context [analyze|optimize|reset]
Modes
analyze (default)
Reviews context files and reports optimization opportunities without making changes.
Checks:
- Token count in CLAUDE.md
- Stale or outdated information
- Redundant/duplicated content
- Import chain depth
- Knowledge-core.md size
Output:
Context Analysis Report
=======================
Total tokens: XXXX
Stale content: X sections
Redundant: X items
Potential savings: XX%
Recommendations:
1. Archive section X to knowledge-core.md
2. Remove duplicate Y
3. Consolidate imports Z
optimize
Automatically applies optimizations:
- Archives outdated content
- Removes duplicates
- Consolidates sections
- Updates imports
Safety: Creates backup before changes
reset
Restores template files and clears customizations.
Use for: Starting fresh projects
Warning: Requires confirmation
When to Run
| Trigger | Command |
|---|---|
| Every 50 messages | /context analyze |
| After major refactoring | /context analyze |
| When analysis shows 15%+ savings | /context optimize |
| Task switching | /context optimize |
| New project | /context reset |
Context Engineering Principles
Active Curation
- Remove information not needed for current task
- Archive completed feature docs
- Keep only active patterns
Signal-to-Noise
- High value: Current APIs, active patterns
- Low value: Old experiments, completed tasks
Token Budget
- CLAUDE.md: < 2000 tokens
- knowledge-core.md: Archive storage
- Imports: Max 5 hops
Performance Gains
Based on Anthropic research:
- 39% improvement in task completion
- 84% token reduction possible
- Faster response times
- More accurate outputs
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 · 92 lines · 19 tokens per session scan A e2a619a960d2
context is a command published in the GitHub repository komluk/scaffolding (15 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 436 once invoked, about $0.0001 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-30.
Other commands, from other repositories
set-context
Set the client context so all subsequent analyses are automatically tailored — store client name, industry, size, geography, and key facts.
resume
Resume a programme from its durable ledger.
brain-init
Opt-in bulk mode: documents every undocumented source file as a linked note in turnstile/code/ after an explicit size/staleness warning. The default is lazy -- code notes are written for ticket-touched files when the ticket passes review.
pickup
Where was I? Restores work state from the board and vault -- the in-progress ticket, its implementation state, blockers, and the relevant notes -- ending with the next command to run. (Claude Code's built-in /resume restores a past conversation; this restores the work itself.).
remember
Files a note you dictate into the knowledge vault. You author the content; the curator only files, tags, and links it. Works in both capture modes.
obsidian-graph
Opens the project's turnstile/ folder in Obsidian and points you at Graph View to browse the brain as a linked graph.