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 skills/arpitnath/claude-capsule-kit/deep-contextnpx skills add arpitnath/claude-capsule-kit --skill deep-contextgit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/deep-context)<a href="https://agentmods.dev/skills/arpitnath/claude-capsule-kit/deep-context"><img src="https://agentmods.dev/badge/skills/arpitnath/claude-capsule-kit/deep-context.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.00047 | $0.02898 |
| Opus 5 | $0.00023 | $0.01449 |
| Sonnet 5 | $0.00009 | $0.00580 |
| Haiku 4.5 | $0.00005 | $0.00290 |
Grade A, and why
deep-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 5d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Context Builder
You are a Deep Context Builder responsible for systematically building comprehensive codebase understanding through multiple layers of context gathering instead of overwhelming your main context window.
Purpose
Problem: Building codebase understanding by reading files sequentially overwhelms context, misses relationships, and doesn't persist knowledge.
Solution: Multi-layer context building using Capsule (automatic), progressive reading, dependency analysis, and specialist agents—each with fresh context.
When to Use This Skill
Auto-triggers on keywords:
- "don't have context", "you don't have enough context"
- "understand the codebase", "learn about this system"
- "need background", "how does this work"
- "explain the architecture", "what's the structure"
Context indicators:
- User says you're missing understanding
- Complex task needs architectural knowledge
- Unfamiliar part of codebase
- Need to understand before implementing
Manual invocation: /deep-context
The Multi-Layer Context Building System
Layer 1: CAPSULE CONTEXT (Automatic)
Goal: Review what Capsule has already provided
At session start, session-start.js automatically injects:
- Last Session — Summary of most recent session
- Top Discoveries — Most-accessed architectural insights
- Recent Files — Last 3 files worked on
- Team Activity (crew mode) — What other teammates have been doing
What to check:
- Review the injected context for past decisions and patterns
- Don't re-read files already mentioned in injected context
- Build on discoveries from previous sessions
- Check for related team work (in crew mode)
Output: Historical + session context, automatically provided
Layer 2: PROGRESSIVE READER (Large Files)
Goal: Understand file structure WITHOUT reading entire files
For large files (>50KB):
Step 1: List file structure
$HOME/.claude/bin/progressive-reader --path <file> --list
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.
- 5d ago First seen · 447 lines · 47 tokens per session scan A 208c110451be
deep-context is a skill published in the GitHub repository arpitnath/claude-capsule-kit (90 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 2,898 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory-consolidate
Reflective consolidation pass over Serena memory files. Separates durable context (preferences, working style, key relationships, recurring workflows) from dated context (projects, deadlines, one-off tasks), merges duplicate topic files onto the richer path, converts relative dates to absolute ones, and tidies…
memory-enhancement
Manage memory citations, verify code references, and track confidence scores. Use when adding citations to memories, checking memory health, or verifying code references are still valid. Use when you say "add a citation", "verify this memory's code refs", "check memory health". Do NOT use for searching or creating…
memory
Thin router for the tiered memory system. Points callers at the focused sub-skills for each operation, Tier 1 search, the reflexion write path, the memory-first gate, maintenance, and consolidation. Use when you ask "what do we know about X", "recall prior context", or "search memory" and are not sure which operation…
research-and-incorporate
Research external topics, create comprehensive analysis, and incorporate learnings into Serena and Forgetful memory systems. Use when you say "research and incorporate {topic}", "study {topic} and add to memory", "deep dive on {topic}", or "learn about {topic} for the project". Works on external concepts, frameworks…
curating-memories
Guidance for maintaining Forgetful record quality and in-file Serena supersession markers. Covers updating outdated records, marking obsolete content, and linking related knowledge. Use when you say "how do I update a memory", "how do I mark a memory obsolete", or "how do I deduplicate Forgetful memories". Do NOT use…