Borrowing it
Nothing to install: this file belongs to SCStelz/security-investigator. 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/SCStelz/security-investigator/main/.github/skills/honeypot-investigation/SKILL.mdgit clone --depth 1 https://github.com/SCStelz/security-investigatorWrote 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/scstelz/security-investigator/honeypot-investigation)<a href="https://agentmods.dev/skills/scstelz/security-investigator/honeypot-investigation"><img src="https://agentmods.dev/badge/skills/scstelz/security-investigator/honeypot-investigation/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/scstelz/security-investigator/honeypot-investigation"><img src="https://agentmods.dev/badge/skills/scstelz/security-investigator/honeypot-investigation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 548 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 557 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00094 | $0.05720 |
| Opus 5 | $0.00047 | $0.02860 |
| Sonnet 5 | $0.00019 | $0.01144 |
| Haiku 4.5 | $0.00009 | $0.00572 |
Grade A, and why
honeypot-investigation 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 13d 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Honeypot Investigation Agent - Instructions
Purpose
This agent performs comprehensive security analysis on honeypot servers to assess attack patterns, threat intelligence, vulnerabilities, and defensive effectiveness. Honeypots are decoy systems designed to attract attackers and provide early warning of emerging threats.
📑 TABLE OF CONTENTS
- Critical Workflow Rules - Start here!
- Investigation Parameters - Input requirements
- Execution Workflow - Complete process with time tracking
- KQL Query Library - Validated query patterns
- Report Template - Executive markdown structure
- Error Handling - Troubleshooting guide
- Visualization Options - Heatmap and Geomap skills
⚠️ CRITICAL WORKFLOW RULES - READ FIRST ⚠️
Before starting ANY honeypot investigation:
- ALWAYS calculate date ranges correctly (use current date from context)
- ALWAYS track and report time after each major step (mandatory per main instructions)
- ALWAYS run independent queries in parallel (drastically faster execution)
- ALWAYS save intermediate results to temp/ (enables debugging and auditing)
- ALWAYS use
create_filefor reports (NEVER use PowerShell terminal commands)
Date Range Rules (from main copilot-instructions):
- Real-time/recent searches: Add +2 days to current date for end range
- Example: Current date = Dec 12, 2025; Last 48 hours =
datetime(2025-12-10)todatetime(2025-12-14)
Investigation Parameters
Required Inputs
| Parameter | Description | Example |
|---|---|---|
| Honeypot Name | Server/device name | honeypot-server |
| Time Range | Investigation period | last 48 hours, last 7 days |
Automatic Derivations
- Start Date: Current date - time range
- End Date: Current date + 2 days (per date range rules)
- Output File:
reports/honeypot/Honeypot_Report_<hostname>_<timestamp>.md - Temp Files:
temp/honeypot_ips_<timestamp>.json,temp/honeypot_data_<timestamp>.json
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.
- 13d ago First seen · 571 lines · 94 tokens per session scan A dae4e57e57f0
honeypot-investigation is a skill published in the GitHub repository SCStelz/security-investigator (245 stars, last pushed 4d ago), licensed MIT. It adds 94 tokens to every session and 5,720 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…