Borrowing it
Nothing to install: this file belongs to Nebulock-Inc/agentic-threat-hunting-framework. 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/Nebulock-Inc/agentic-threat-hunting-framework/main/AGENTS.mdgit clone --depth 1 https://github.com/Nebulock-Inc/agentic-threat-hunting-frameworkWrote 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/nebulock-inc/agentic-threat-hunting-framework/agents-md)<a href="https://agentmods.dev/instructions/nebulock-inc/agentic-threat-hunting-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/nebulock-inc/agentic-threat-hunting-framework/agents-md/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/instructions/nebulock-inc/agentic-threat-hunting-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/nebulock-inc/agentic-threat-hunting-framework/agents-md.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.07721 | $0.07721 |
| Opus 5 | $0.03861 | $0.03861 |
| Sonnet 5 | $0.01544 | $0.01544 |
| Haiku 4.5 | $0.00772 | $0.00772 |
Grade A, and why
agentic-threat-hunting-framework AGENTS.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 10d 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 — 805 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Context for AI Assistants Using ATHF
Purpose: This file provides AI assistants with context about threat hunting repositories using the Agentic Threat Hunting Framework (ATHF).
Repository Overview
This repository contains threat hunting investigations using the LOCK pattern (Learn → Observe → Check → Keep).
AI assistants should:
- 🔧 ALWAYS activate the virtual environment FIRST - Run
source .venv/bin/activatebefore anyathfcommands (verify withwhich athf) - Read knowledge/hunting-knowledge.md - Expert hunting frameworks and analytical methods
- Browse past hunts - Search hunt history before suggesting new hypotheses
- Reference lessons learned when generating queries
- Use environment.md to understand available data sources
- Focus on behaviors and TTPs (top of Pyramid of Pain), not indicators
🚨 MANDATORY: Use ATHF CLI Commands & Agents
CRITICAL REQUIREMENT: AI assistants MUST use athf CLI commands or athf agent run for ALL tasks that have corresponding CLI functionality. Direct file manipulation is prohibited for framework-managed operations.
✅ ALWAYS Use CLI For
| Task Category | CLI Command | ❌ Never Use |
|---|---|---|
| Hunt creation | athf hunt new --non-interactive |
Write tool, Edit tool |
| Investigation creation | athf investigate new --non-interactive |
Write tool, Edit tool |
| Research execution | athf research new --topic "..." |
Manual web search, Write tool |
| Hypothesis generation | athf agent run hypothesis-generator --threat-intel "..." |
Manual hypothesis drafting |
| Duplicate checking | athf similar "keywords" |
Grep, manual search |
| Context loading | athf context --hunt H-XXXX |
Multiple Read operations |
| Coverage analysis | athf hunt coverage |
Manual ATT&CK counting |
| Hunt validation | athf hunt validate H-XXXX |
Manual YAML parsing |
| Hunt search | athf hunt search "keyword" |
Grep, manual file search |
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.
- 10d ago First seen · 805 lines · 7,721 tokens per session scan A d2462a2e5303
agentic-threat-hunting-framework AGENTS.md is an instructions file published in the GitHub repository Nebulock-Inc/agentic-threat-hunting-framework (370 stars, last pushed 6d ago), licensed MIT. It adds 7,721 tokens to every session, about $0.0386 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
agent-compass pr-workflow.instructions.md
Instructions for me-cedric/agent-compass: For PR creation, default base branch is develop. Assign the PR to yourself with --assignee @me. If reviewers are not specified, ask for at least one and list likely repo contributors. Use only labels that exist in gh label list.
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).
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).
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.