Borrowing it
Nothing to install: this file belongs to MrLesk/agents-council. 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/MrLesk/agents-council/main/.agents/skills/context-hunter/SKILL.mdgit clone --depth 1 https://github.com/MrLesk/agents-councilWrote 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/mrlesk/agents-council/context-hunter)<a href="https://agentmods.dev/skills/mrlesk/agents-council/context-hunter"><img src="https://agentmods.dev/badge/skills/mrlesk/agents-council/context-hunter.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.00039 | $0.01157 |
| Opus 5 | $0.00019 | $0.00579 |
| Sonnet 5 | $0.00008 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
context-hunter 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Hunter
Before writing code, run a focused discovery loop. Do not load everything. Find the right files.
Complexity Gate
Classify task complexity first:
L0 (trivial): typos, renames, copy-only edits, obvious single-line fixes with no behavior change.L1 (moderate): behavior changes in one bounded area.L2 (high-risk): cross-module changes, data semantics, refactors, architecture-impacting work.
Output by level:
L0: no context brief, proceed directly.L1: write a micro-brief.L2: write a full context brief.
Re-evaluate level during discovery and implementation. If new evidence shows higher complexity than initially classified, upgrade the level and apply the stricter workflow.
Core Behavior
Act like a senior engineer who asks the next useful question:
- Assess completeness: Check whether the request omits expected concerns seen in analogous code.
- Discover selectively: Read the minimum set of relevant files.
- Validate assumptions: Confirm with tests/config/history.
- Synthesize: Capture findings before coding for
L1/L2.
Discovery Workflow (Before Coding)
1) Assess Request Completeness
Ask: "What is likely missing?"
Examples:
- Similar endpoints include auth/validation. Is that expected here?
- This area uses soft-delete semantics. Should this operation follow that?
- Similar flows emit telemetry/error states. Should this change do the same?
- Existing module boundaries suggest a different placement. Is current request still correct?
2) Run Targeted Discovery
Prioritize these in order:
- Find analogous implementations and copy their structure.
- Trace data flow for similar features end-to-end.
- Identify reusable utilities before creating new helpers.
- Inspect nearby tests to infer team priorities and edge cases.
- Read recent commits in the same area for current direction.
Portable discovery actions:
- Search for feature/domain terms in relevant directories.
- Enumerate nearby files in the affected area.
- Inspect recent change history for touched paths.
- Run targeted validation first, then broader project checks as needed.
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 · 142 lines · 39 tokens per session scan A 8f634b3adef2
context-hunter is a skill published in the GitHub repository MrLesk/agents-council (66 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,157 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
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
add-openagents
Add the OpenAgents Workspace channel so this NanoClaw Agent Group can be driven from an OpenAgents Workspace.
openagents-workspace
OpenAgents Workspace collaboration tools — shared files, browser, and multi-agent coordination. Use when: sharing files or reports, browsing websites, reading shared files, checking workspace agents, or collaborating with other agents via @mentions.
map
Discover work structure by approaching goals and finding blockers — emergent planning through action, not top-down decomposition.
triaging-mutants
Use when mutation testing reveals survived mutants — guides deep analysis of whether each mutant signals a missing test, a design improvement opportunity, or an equivalent mutation.
ubiquitous-language
Use when evaluating the ubiquitous language in a codebase - produces a glossary of domain terms with references and commentary on inconsistencies, awkward names, or overlapping concepts.