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.
npx agentmods add instructions/tarekmo0/hunterstick/claude-mdgit clone --depth 1 https://github.com/tarekmo0/HunterStickWrote 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/instructions/tarekmo0/hunterstick/claude-md)<a href="https://agentmods.dev/instructions/tarekmo0/hunterstick/claude-md"><img src="https://agentmods.dev/badge/instructions/tarekmo0/hunterstick/claude-md.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 | $0.00233 | $0.00233 |
| Opus 5 | $0.00117 | $0.00117 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
HunterStick CLAUDE.md 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.
What it actually says
HunterStick
The instructions for this project live in AGENTS.md. Read it now, in full,
before doing anything else.
This file exists only because Claude Code loads it automatically. It is deliberately a pointer: one canonical instruction set, so the two can never drift.
Claude Code specifics — everything else is in AGENTS.md:
.claude/skills/*/SKILL.mdfrontmatter descriptions are what Claude Code matches on, so saying "test IDOR on /api/orders" fires the right skill without naming a path.self-check.pynow enforces that theAGENTS.mdrouter names only real skills and that its advertised count matches the dispatchers the runtime exposes; keeping each description in step with its router row is still yours to do. Runtimes that load rootAGENTS.mduse the same router; runtimes without instruction or skill discovery must be pointed toAGENTS.mdexplicitly..mcp.jsonwires the browser and Burp MCP servers used by application mapping.
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.
- 5d ago First seen · 18 lines · 233 tokens per session scan A 30bea18a6b28
HunterStick CLAUDE.md is an instructions file published in the GitHub repository tarekmo0/HunterStick (13 stars, last pushed yesterday), licensed MIT. It adds 233 tokens to every session, about $0.0012 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).