pentest-recon
Mapping the attack surface of an authorized target: subdomains, open ports, running services and versions, the technology stack, and every input surface, passive sources before active ones, the quietest technique that answers the question. Read before enumerating a target.
- License 许可
- Apache-2.0
- 所属仓库
- enowdev/enowxcli
- 最近更新
- 2026-10-06
- Stars
- ★ 67
- Forks
- 21
01 前言 Front Matter
- name
- pentest-recon
- description
- Mapping the attack surface of an authorized target: subdomains, open ports, running services and versions, the technology stack, and every input surface, passive sources before active ones, the quietest technique that answers the question. Read before enumerating a target.
02 资源文件 6
- 参考文档references/style_guide.md6.8 KB
- 脚本scripts/draw_2d.py8.2 KB
- 脚本scripts/draw_grid.py11.9 KB
- 脚本scripts/draw_interactions.py17.0 KB
- 脚本scripts/draw_scaffold.py15.4 KB
- 脚本scripts/render_3d.py22.9 KB
03 SKILL.md 正文
Reconnaissance
Your job is mapping, not exploiting. You enumerate what is exposed so the testing stages and the final report can rely on it.
Scope first. Work only against hosts, domains and addresses the engagement authorizes. A target not on the list is out of bounds, stop and ask.
What to map
- Domains and hosts. Subdomains (passive certificate-transparency and DNS sources before brute force), the addresses they resolve to, and which are in scope.
- Services and versions. Open ports, the service on each, and its version.
Prefer a light
httpx/banner grab to an aggressive full scan; match the intensity to the rules of engagement. - The stack. Server, framework, language, CDN, WAF, third-party components and their versions, anything a known-vulnerability check can use later.
- The input surface. Every endpoint, parameter, form field, header, cookie and upload. This map is what the testing stages work from.
How
- Passive before active: certificate transparency, DNS, public sources, and the application's own responses tell you a great deal before you send a probe.
- Record every finding with where and how you found it. Note anything that
looks sensitive or accidentally exposed (an open
.git, a stack trace, a debug endpoint) but do not exploit it, hand it to the right stage. - Stay within the rate limits. Loud recon gets the engagement noticed and can knock over a fragile target.
Tools you might run through bash (only those installed and in scope):
dig/host, httpx, nmap (light), whatweb, subfinder. Record versions
and the exact commands so the report is reproducible.
04 同仓库更多 Skills
demo-skill
Project-scope demo skill for tests.
writing
Writing words people read: the specific thing instead of claims, words to drop, sentences, interface copy (buttons, labels, errors, empty states, confirmations), page copy, notifications and emails, alt text and link text, numbers and dates, words that translate well, documentation and voice. Read before writing a page's copy, an interface's text or a document.
ui
Designing or restyling an interface: direction, layout, type, colour, icons, components, states, responsive behaviour. Read before building a page, a screen or a set of components.
ui-themes
Light and dark themes, and colour that holds in both: tokens with a value per theme, and what each kind of content needs to stay visible (icons, SVG drawings and line art, logos, photos, screenshots, charts, code, maps, borders, shadows, focus, form controls), switching without a flash, and checking both. Read before building a second theme or a theme toggle, and before any drawing, logo or chart on a page that has two themes.
ui-structure
Structure before styling: the blueprint written before any interface code (the screen's job, the regions its kind of page needs, their order and why, the layout skeleton in numbers, the components and their states), the anatomy and order of a homepage, a dashboard, a list, a detail page, settings, a form, sign-in, pricing, docs, an article and a checkout, and how to turn the blueprint into code (tokens, layout primitives, components, sections, page). Read first, before building or rebuilding any page or screen.
ui-stack-vue
Building interfaces in Vue 3 and Nuxt: project layout, script setup with typed defineProps, defineEmits and defineModel, attribute fallthrough, slots and scoped slots, template refs, ref, reactive and computed, watch versus watchEffect, composables and VueUse, provide and inject, Pinia, keyed v-for, transitions, Nuxt 4 (app directory, pages, layouts, useFetch and useAsyncData keys, $fetch in handlers, server routes, runtime config, useSeoMeta, NuxtImg, middleware), VeeValidate forms, Reka UI and Nuxt UI, testing, vue-tsc, and the traps. Read when the project uses Vue or Nuxt.