AGENT SKILL

runtime-surface-probing

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.

License 许可
MIT
所属仓库
Eliyce/paqad-ai
最近更新
2026-11-13
Stars
★ 8
Forks
0

01 前言 Front Matter

name
runtime-surface-probing
metadata
{ "cacheable": "false", "model_tier": "medium", "paqad-meta": "skill.meta.yaml", "output_format": "markdown" }
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.

02 资源文件 7

03 SKILL.md 正文

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

04 同仓库更多 Skills

Eliyce
Eliyce/paqad-ai

sample-skill

Sample bundled skill fixture

★ 8
Eliyce
Eliyce/paqad-ai

processing-invoices

Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.

★ 8
Eliyce
Eliyce/paqad-ai

processing-invoices

Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.

★ 8
Eliyce
Eliyce/paqad-ai

understand-idea

Chat and Claude Code: Step 1 of the discover journey: clarifies the goal, who benefits, success and constraints into the idea block. Use when the journey directs it to step 1, not directly.

★ 8
Eliyce
Eliyce/paqad-ai

size-work

Chat and Claude Code: Suggest a size for a ticket from comparable finished work, as a labelled suggestion the team still owns. Use it when someone asks "how big is this?", "roughly how much work is ABC-12?", or wants a backlog item sized. It finds the team's sizing scale at first use, picks two to five of the closest finished tickets with links, and gives a size or range with the drivers behind it and a confidence of low, medium or high, lowered and explained when the area's documents are template text. Every result is labelled a suggested size, never a date or a commitment. It writes nothing into the size field unless the user says "set it", and it refuses to overwrite an existing size unless the user asks to replace it. Produces the sizing block of the record.

★ 8
Eliyce
Eliyce/paqad-ai

refine-ticket

Chat and Claude Code: Improve one or more existing tracker tickets without losing the author's intent. Use it when someone wants a ticket read, diagnosed and tidied up ("this ticket is vague", "fix up ABC-12", "split this, it's too big"). It reads each ticket in full and snapshots it with its last-updated time, says what is wrong with evidence, and proposes a field-by-field before and after change set limited to summary, description, labels, parent, links and new child tickets on a split. It writes nothing until an explicit "apply it" bound to that exact change set, re-checks the ticket for conflicting edits just before writing, never replaces rich descriptions with plain text, never deletes or closes a ticket, and reads each ticket back after applying. Produces the existing and changes blocks of the record.

★ 8