context-hunter

context-hunter is a skill for Claude Code, Codex from foryourhealth111-pixel/Vibe-Skills. It costs 32 tokens per session (395 once invoked), scanned A, original, Apache-2.0.

A codebase investigation skill that finds existing patterns, conventions, utilities, tests, and configuration before code is changed.

In plain words
What is it for?
Use it before implementing features, fixing bugs, or refactoring code when you need to understand how similar problems are already solved.
Why use it?
It reduces the risk of adding code that conflicts with the project's established design or repeats something that already exists. It also helps check assumptions about data flow, validation, testing, and database rules.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it before implementing features, fixing bugs, or refactoring code when you need to understand how similar problems are already solved.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/foryourhealth111-pixel/vibe-skills/context-hunter
About the project

Vibe-Skills is a collection and routing system that helps AI agents discover, select, and coordinate specialized skills for completing tasks. It is intended for agents that need to organize workflows across many installed capabilities. The catalogue entries are skills and an agent belonging to this system.

foryourhealth111-pixel/Vibe-Skills · 3,252 stars · on GitHub

Install

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.

Any agent
npx skills add foryourhealth111-pixel/Vibe-Skills --skill context-hunter
Clone the repo
git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for context-hunter

README.md
[![agentmods](https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/context-hunter/github.svg)](https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/context-hunter)
Your own site
<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/context-hunter"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/context-hunter/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.

agentmods 80×15 button for context-hunter

Your own site · 80×15
<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/context-hunter"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/context-hunter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 395 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00395
Opus 5 $0.00016 $0.00198
Sonnet 5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00040

Measured 12d ago against content hash eb8866f01839, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 12d 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.

bundled/skills/context-hunter/SKILL.md · 61 lines

What it actually says

Context Hunter

Before writing code, investigate how similar problems are already solved in this codebase.

Before Implementation

Discover Existing Patterns

  1. Find analogous features: Search for code that solves similar problems. Study it before proposing your approach.
  2. Trace data flow: How does similar data move through the system? Note caching, validation, and error handling patterns.
  3. Identify utilities: Search for existing helpers before creating new ones.

Detect Unwritten Conventions

Look for implicit rules encoded in the codebase:

  • Schema patterns: deleted_at columns indicate soft-deletion. Audit columns indicate tracking requirements.
  • Naming patterns: Note consistency in user_id vs userId vs userID.
  • Test patterns: What's tested thoroughly reveals team priorities.

Verify Assumptions

  • Run the test suite to understand current state
  • Check linter and formatter configs
  • Read recent commits in affected areas
  • Examine database schemas for constraints

During Implementation

Match Existing Code

Your changes should be indistinguishable from existing code:

  • Use the same patterns, abstractions, and utilities
  • Follow the same error handling approach
  • Respect module boundaries
  • Match naming conventions exactly

Surface Concerns

When you discover conflicts between requirements and existing patterns:

  • Ask clarifying questions before proceeding
  • Flag risks you've identified
  • Offer alternatives that align with codebase conventions

Checklist

Before proposing changes, confirm:

  • Studied analogous features in the codebase
  • Checked for reusable utilities
  • Reviewed test patterns for similar functionality
  • Noted naming and schema conventions
  • Verified approach matches existing patterns
Changes

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.

  1. 12d ago First seen · 61 lines · 32 tokens per session scan A eb8866f01839

Subscribe to this mod's changes

context-hunter is a skill published in the GitHub repository foryourhealth111-pixel/Vibe-Skills (3,252 stars, last pushed 11d ago), licensed Apache-2.0. It adds 32 tokens to every session and 395 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.