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 Eliyce/paqad-ai --skill runtime-surface-probinggit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/runtime-surface-probing)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/runtime-surface-probing"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/runtime-surface-probing/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/eliyce/paqad-ai/runtime-surface-probing"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/runtime-surface-probing.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.00018 | $0.00503 |
| Opus 5 | $0.00009 | $0.00251 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
runtime-surface-probing scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
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.mdbefore deciding whether a reachable path is risky. - Read stack-specific tool references for browser validation when the stack ships them.
Procedure
- Run
scripts/probe-surfaces.sh <base-url>— GET-only probe ofassets/probe-paths.txt; exits 1 if the base is unreachable. - Review the
status | pathoutput and decide which non-404 results indicate unintended public exposure vs expected local-only behavior. - Format findings per
assets/output.template.md— every finding must cite path and numeric status code. - Validate with
scripts/lint-findings.sh. - 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.mdscripts/probe-surfaces.shscripts/lint-findings.shassets/probe-paths.txtassets/output.template.mdagents/openai.yaml
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 63 lines · 18 tokens per session scan A 40eaf5fe22d0
runtime-surface-probing is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 503 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
browser-automation
A browser-automation workflow that detects the terminal environment and chooses a browser control tool. It supports opening pages, taking snapshots, clicking, filling fields, and other checks.
playwright-cli
Skill "playwright-cli" from Insajin/autopus-adk, covering browser automation with playwright-cli, quick start, commands, core and navigation.
structured-extraction
Extract structured data from web pages using browser snapshot and text tools, then process it into tables, comparisons, or summaries using Python.
web-researcher
Web research tools for fetching and reading web pages. Use when the agent needs to browse the web or make HTTP API calls.
playwright-mcp
Complete guide for using Playwright MCP to automate browsers inside AI agent workflows. Use this skill whenever the agent needs to: navigate web pages, fill forms, click elements, take screenshots, mock API responses, manage cookies/localStorage, save auth state, generate Playwright test code, record video/traces…
Web Research
Browser-driven or scraping-based skill for real-time internet extraction using Playwright and HTTP-based fetching.