Borrowing it
Nothing to install: this file belongs to greenpau/go-authcrunch. 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/greenpau/go-authcrunch/main/.codex/skills/threat-hunting/SKILL.mdgit clone --depth 1 https://github.com/greenpau/go-authcrunchWrote 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/greenpau/go-authcrunch/threat-hunting)<a href="https://agentmods.dev/skills/greenpau/go-authcrunch/threat-hunting"><img src="https://agentmods.dev/badge/skills/greenpau/go-authcrunch/threat-hunting/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/skills/greenpau/go-authcrunch/threat-hunting"><img src="https://agentmods.dev/badge/skills/greenpau/go-authcrunch/threat-hunting.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.00092 | $0.04219 |
| Opus 5 | $0.00046 | $0.02109 |
| Sonnet 5 | $0.00018 | $0.00844 |
| Haiku 4.5 | $0.00009 | $0.00422 |
Grade A, and why
threat-hunting 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 yesterday.
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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Hunting
Operating Posture
Treat every authentication shortcut, authorization shortcut, redirect, token source, cookie, forwarded header, parser, cache, and cryptographic decision as a security boundary until proven otherwise.
Skepticism is a verification mode, not a reason to dismiss a report. Translate claims into falsifiable checks, then test or inspect the exact runtime behavior.
Core authorization question — answer it for every protected path:
- What object is being authorized?
- What object is later served, proxied, redirected to, or trusted?
- Are those objects represented by the same normalized value?
- Which checks execute before token validation, ACL evaluation, or signature verification?
Use the repo-local coding-directives skill for fixes, testing-and-ci for
test selection, and scripts-and-automation for repository tooling.
Use local-password-authentication
when reviewing local password enumeration, bcrypt costs, or dummy comparisons.
Severity Rubric
| Severity | Criteria |
|---|---|
| Critical | Unauthenticated authn/authz bypass, token forgery, RCE, secret exfiltration |
| High | Authenticated privilege escalation, open redirect to authn bypass, session fixation |
| Medium | Unintended token/secret leakage outside explicit admin debug diagnostics, missing cookie security flags, SSRF with limited reach |
| Low | Defense-in-depth gap, hardening issue with no direct exploit path |
| Info | Coding pattern risk, missing test coverage, informational finding |
Workflow
1. Scope the Hunt
Identify the security boundary and all attacker-controlled inputs before searching code.
Request inputs:
- URL fields:
Path,RawPath,RequestURI, query, fragment, scheme, host, absolute-form targets, HTTP/2 pseudo-headers (:path,:authority) - Headers:
Host,X-Forwarded-*, auth and API-key headers, cookies, content-type, client-IP headers - Body fields: JSON maps, form values, SAML/OAuth payloads, metadata, profile/admin API inputs
- Protocol upgrade paths: WebSocket
Upgrade, gRPC framing, chunked encoding
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 442 lines · 92 tokens per session scan A 4a1efa987a40
threat-hunting is a skill published in the GitHub repository greenpau/go-authcrunch (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 92 tokens to every session and 4,219 once invoked, about $0.0005 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-09-13.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.