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 skills add mahuttha/offensive-recon --skill recon-pipelinegit clone --depth 1 https://github.com/mahuttha/offensive-reconWrote 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/mahuttha/offensive-recon/recon-pipeline)<a href="https://agentmods.dev/skills/mahuttha/offensive-recon/recon-pipeline"><img src="https://agentmods.dev/badge/skills/mahuttha/offensive-recon/recon-pipeline/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/mahuttha/offensive-recon/recon-pipeline"><img src="https://agentmods.dev/badge/skills/mahuttha/offensive-recon/recon-pipeline.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.00069 | $0.01995 |
| Opus 5 | $0.00034 | $0.00997 |
| Sonnet 5 | $0.00014 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
recon-pipeline scanned grade A with 1 finding 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 11d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo nmap -sV -T3 -iL /tmp/recon/phase2-live.txt -oN /tmp/recon/phase2-nmap.txt -oX /tmp/recon/phase2-nmap.xml 2>&1 Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recon Pipeline — Full Multi-Phase Reconnaissance
Orchestrate a complete security reconnaissance workflow across all available tools.
Decision Loop: In-the-Loop (full pipeline requires explicit authorization)
Safety — CRITICAL Authorization Required
Before starting the pipeline:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔍 Recon Pipeline — Full Security Assessment
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
เป้าหมาย (Target): <target-domain>
เฟส (Phases): <1-3 or all>
เครื่องมือที่จะใช้ (Tools to be used):
Phase 1 (Passive): Shodan, Subfinder, WhatWeb (level 1)
Phase 2 (Discovery): Nmap (standard mode)
Phase 3 (Assessment): Nuclei (ncsa+high), Nikto, SQLMap (detect only, if forms found)
⚠️ Phase 2-3 จะส่ง traffic ไปยังเป้าหมาย (will send traffic to target)
⚠️ ต้องได้รับอนุญาตจากเจ้าของเป้าหมาย (authorization from target owner required)
ยืนยันดำเนินการ? (Confirm execution?) [y/N]
Do NOT proceed without explicit user confirmation.
Arguments
<target-domain>— Primary domain to assess (REQUIRED)--phases— Which phases to run (default:all)--skip-sqlmap— Skip SQL injection testing
Pipeline Architecture
Phase 1: Passive Recon (no traffic to target)
├── Shodan API lookup (host info, known vulns)
├── Subfinder (subdomain enumeration)
└── WhatWeb level 1 (technology detection)
│
▼ (discovered subdomains + IPs)
Phase 2: Discovery (active scanning)
├── httpx (live host verification)
└── Nmap standard scan (ports + services)
│
▼ (live hosts + open ports + services)
Phase 3: Assessment (vulnerability scanning)
├── Nuclei (NCSA templates + critical/high)
├── Nikto (web server vulnerabilities)
└── SQLMap detect (if web forms found, optional)
│
▼
Finding Analyst Agent
├── Deduplicate across tools
├── Map to OWASP / NCSA categories
├── Assign severity ratings
└── Generate combined report
Execution Steps
Phase 1: Passive Recon
Use the recon-orchestrator agent to coordinate:
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.
- 11d ago First seen · 214 lines · 69 tokens per session scan A cc10126f2a69
recon-pipeline is a skill published in the GitHub repository mahuttha/offensive-recon (4 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 1,995 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…