Skip to content
Back to skills

Runtime Surface Probing

ASecurity

Plan and interpret safe runtime checks against a locally running application.

  • 8 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agents

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add Eliyce/paqad-ai --skill runtime-surface-probing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Runtime Surface Probing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Runtime Surface Probing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/eliyce-runtime-surface-probing/badge)](https://www.skillsdirectory.com/skills/eliyce-runtime-surface-probing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: runtime-surface-probing
description: Plan and interpret safe runtime checks against a locally running application.
model_tier: medium
triggers:
  - workflow:
      - pentest
cacheable: false
cache_key_inputs: []
output_format: markdown
input_schema:
  target_url:
    type: string
    required: true
    description: Base URL for the locally running application.
  runtime_artifact_paths:
    type: path[]
    required: false
    description: Artifacts produced by runtime-check scripts.
---

## 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

Use this 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`

Files in this skill

  • SKILL.md2.2 KB
  • agents/openai.yaml131 B
  • assets/output.template.md362 B
  • assets/probe-paths.txt416 B
  • references/runtime-surface-checks.md2.4 KB
  • scripts/lint-findings.sh1.1 KB
  • scripts/probe-surfaces.sh1.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.