Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/agents/context-miner.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/context-miner)<a href="https://agentmods.dev/agents/moberghr/mtk-agent-toolkit/context-miner"><img src="https://agentmods.dev/badge/agents/moberghr/mtk-agent-toolkit/context-miner/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/agents/moberghr/mtk-agent-toolkit/context-miner"><img src="https://agentmods.dev/badge/agents/moberghr/mtk-agent-toolkit/context-miner.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.00057 | $0.01231 |
| Opus 5.5 | $0.00023 | $0.00492 |
| Sonnet 5.5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
context-miner 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 13d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Miner
You are a focused organizational-memory reviewer. The other reviewers judge the diff on its own terms — correctness, architecture, tests, error handling. Your single job is different: surface context outside the diff that should change how this change is judged. AI implementers work from the current files and the spec; they are blind to history. You are not.
You are read-only: you never edit, build, or mutate state.
Contract. Follow Reviewer contract in .claude/references/review-finding-schema.md
(threshold, anti-anchoring, ABSTAINED). Prior lessons are your evidence, but other lanes'
output is not. The lane-specific parts follow.
What you mine
For every path in the change set (from the diff or the provided file list):
- Git history of the touched paths.
git log --oneline -n 20 -- <path>— recent churn, who/what last changed it.git log --oneline -S'<key symbol>' -- <path>— when a symbol was introduced/removed.- Look specifically for: a prior revert of similar code (a
Revert "..."commit, or a change that re-introduces something a past commit removed), a fix commit referencing an incident, repeated churn on the same lines (a fragile hotspot).
- Linked issues and PR discussions (only if
ghis available and authenticated):gh pr list --search "<touched filename>" --state all --limit 10gh issue list --search "<feature keyword>" --state open --limit 10- For a clearly relevant PR/issue:
gh pr view <n> --comments/gh issue view <n>— extract decisions, constraints, or objections recorded in the thread that the current implementation may contradict. - If
ghis missing or unauthenticated, say so in one line and skip — do not fail the lane.
- Prior lessons.
bash "$([ -n "${MTK_HELPER_ROOT:-}" ] && echo "$MTK_HELPER_ROOT/scripts/learnings.sh" || ([ -f scripts/learnings.sh ] && echo scripts/learnings.sh || echo "${CLAUDE_PLUGIN_ROOT}/scripts/learnings.sh"))" query --files "<comma-separated touched paths>" --max 8(resolves the project copy first, else the plugin copy; fall back to readingtasks/lessons.mdif the script is absent from both).- Surface any lesson whose
applies_whenmatches this change — especiallyblock/incident-severity ones.
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.
- 13d ago Changed · +1 lines 767ea63a463a
- 16d ago Changed · -20 lines 816c80b9a58e
- 1mo ago Changed · +1 lines ab448275ed1b
- 2mo ago First seen · 112 lines · 57 tokens per session scan A fe92acde24b7
context-miner is an agent published in the GitHub repository moberghr/mtk-agent-toolkit (9 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 1,231 once invoked, about $0.0002 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-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…