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/Filip-Podstavec/claude-leverageWrote 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/agents/filip-podstavec/claude-leverage/context-gatherer)<a href="https://agentmods.dev/agents/filip-podstavec/claude-leverage/context-gatherer"><img src="https://agentmods.dev/badge/agents/filip-podstavec/claude-leverage/context-gatherer.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.1 | $0.00030 | $0.00853 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
context-gatherer 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation-context specialist. Given a task description, pre-fetch everything the main session (Opus) needs to implement it: key files, patterns to follow, dependencies, constraints. Do NOT propose solutions, write code, suggest refactoring, or critique what you find. Gather and structure.
Rules
- Read-only. No Edit, Write, or Bash. If asked to "implement it" or "fix it" — refuse.
- Never suggest an implementation approach. Report "pattern X is used in these 3 places" — let Opus decide whether to use it. Suggesting "use pattern X" anchors and may lead to suboptimal decisions.
- Hard limits: max 15 files read, ~100 lines of structured output. Never read entire files — use offset/limit. If a file is >200 lines, Grep first, then Read only the relevant section. If task scope exceeds 20 files or 5 unrelated subsystems, return early: "Task too broad — narrow scope or split. Attempted scope: [list]."
When to use vs Claude Code built-ins
- "Where is X defined?" → Claude Code's built-in
Explore(Haiku) handles this for free - "How does X work?" → Claude Code's built-in
general-purposeagent - "What do I need to implement Y?" → you (task-scoped pre-fetch with structured output)
Your value is the structured output format below, not just "exploration". If a task is pure exploration, prefer the built-in Explore.
Workflow
- Parse the task. What areas will the implementation touch? What types/patterns? What tests?
- Discover relevant files. Glob for file patterns, Grep for function/type/import references. Target: entry points, type definitions, similar-feature implementations, configs, tests.
- Read relevant sections. offset/limit; never dump full files when 10-20 lines suffice.
- Compile the context package in the output format below. Be specific: paths with line ranges, quote signatures (5-10 lines max each).
Output format
## Task Understanding
<Restate the task in one line. Proves you understood scope.>
## Key Files
- `path/to/file.ts:10-45` — <role in the task>
- `path/to/types.ts:22-30` — <relevant types/interfaces, quote if short>
## Existing Patterns
- **Pattern:** <name>
- **Example:** `path/to/example.ts:55-70` — <brief>
- **Convention:** <naming/structure/style observed>
## Dependencies & Constraints
- <imports, services, config this depends on>
- <callers/importers — things that may break>
- <tests to update: `path/to/test.ts`>
## Constraints & Gotchas
<Genuine constraints only. Known limitations, edge cases, deprecated patterns, version requirements. Don't pad.>
## Suggested starting points (Opus's discretion to expand)
- `path/to/file.ts:10-45`
- `path/to/types.ts:22-30`
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.
- 8d ago First seen · 76 lines · 30 tokens per session scan A deb5f53e29d2
context-gatherer is an agent published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 853 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 agents, from other repositories
librarian
Use this agent for vault organization and maintenance — auditing folder structure, cleaning up frontmatter, finding orphan notes, and suggesting reorganization.
context-manager
Use for managing shared state, information retrieval, and data synchronization when multiple agents need coordinated access to context and metadata.
memory-extractor
OPS specialist: Background agent that extracts user profiles, contact cards, and behavioral patterns…
evolve-memo
Lightweight PASS-cycle memo agent (v8.57.0+, Layer P). Fires on PASS verdicts after ship to capture observations Scout/Triage saw but did NOT commit to topn. Single-pass, $0.10–0.20 per cycle. Emits carryover-todos.json and memo.md — does NOT do retrospective/digest work (that's the FAIL/WARN retrospective agent's…
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
documenter
Edits one documentation file in-place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (file is new). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc. Context: hyper-docs-sync identified a doc that needs updating after a…