UNPKG

paqad-ai

Version:

Spec-driven development framework — AI agents that think before they type

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

52 lines (37 loc) • 2.06 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
--- name: runtime-surface-probing description: 'Plans and interprets safe runtime checks against a locally running application. Use when a pentest run has the project running and safe probes have executed.' metadata: model_tier: medium cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Interprets safe browser and HTTP probe results so exposed debug, admin, and sensitive-file surfaces become actionable findings instead of raw status codes. ## Use This When During pentest runs when the local project is already running and safe runtime probes have been executed. ## Inputs - Read the runtime artifacts first. - Read `references/runtime-surface-checks.md` before deciding whether a reachable path is risky. - Read stack-specific tool references for browser validation when the stack ships them. ## Procedure 1. Run `scripts/probe-surfaces.sh <base-url>`: GET-only probe of `assets/probe-paths.txt`; exits 1 if the base is unreachable. 2. Review the `status | path` output and decide which non-404 results indicate unintended public exposure vs expected local-only behavior. 3. Format findings per `assets/output.template.md`: every finding must cite path and numeric status code. 4. Validate with `scripts/lint-findings.sh`. 5. Record blocked probes (base unreachable, paths skipped) under `## Coverage Notes`, not as findings. ## Output Contract - Match `assets/output.template.md`: severity, surface, `Path: \`/foo\``, `Status: NNN`, Required action. - Output must pass `scripts/lint-findings.sh` (exit 0). ## Escalate / Stop Conditions - Ask when the provided target URL does not appear to correspond to the project under review. - Warn when debug or sensitive-file paths are reachable even in local mode because deployment drift may expose them elsewhere. - Do not escalate harmless 404s as findings. ## Resources - `references/runtime-surface-checks.md` - `scripts/probe-surfaces.sh` - `scripts/lint-findings.sh` - `assets/probe-paths.txt` - `assets/output.template.md` - `agents/openai.yaml`