component-hunt

component-hunt is a skill for Claude Code, Codex from tarekmo0/HunterStick. It costs 51 tokens per session (170 once invoked), scanned A, original, MIT.

A guided security check for a known web framework or software stack, such as Spring Boot or WordPress. It looks for exposed endpoints, files, settings, and other stack-specific problems.

In plain words
What is it for?
Use it to inspect a fingerprinted server for framework-specific misconfigurations and exposed diagnostic or configuration data.
Why use it?
It focuses testing on common mistakes associated with the technology actually running on a host.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/tarekmo0/hunterstick/component-hunt
Any agent
npx skills add tarekmo0/HunterStick --skill component-hunt
Clone the repo
git clone --depth 1 https://github.com/tarekmo0/HunterStick

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 component-hunt

README.md
[![agentmods](https://agentmods.dev/badge/skills/tarekmo0/hunterstick/component-hunt.svg)](https://agentmods.dev/skills/tarekmo0/hunterstick/component-hunt)
Your own site
<a href="https://agentmods.dev/skills/tarekmo0/hunterstick/component-hunt"><img src="https://agentmods.dev/badge/skills/tarekmo0/hunterstick/component-hunt.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.00170
Opus 5 $0.00026 $0.00085
Sonnet 5 $0.00010 $0.00034
Haiku 4.5 $0.00005 $0.00017

Measured 5d ago against content hash ed6022c42deb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

component-hunt 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.

.claude/skills/component-hunt/SKILL.md · 11 lines

What it actually says

Read skills/vulnerability-testing/component-hunt.md and follow it.

That file is the single body for this skill; this pointer exists only so Claude Code can auto-trigger on the description above. Every other runtime dispatches to the same file through the router table in AGENTS.md.

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. 5d ago First seen · 11 lines · 51 tokens per session scan A ed6022c42deb

Subscribe to this mod's changes

component-hunt is a skill published in the GitHub repository tarekmo0/HunterStick (13 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 170 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens