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 aaronnat23/disp8ch --skill xurl-api-probinggit clone --depth 1 https://github.com/aaronnat23/disp8chWrote 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/aaronnat23/disp8ch/xurl-api-probing)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/xurl-api-probing"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/xurl-api-probing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00166 |
| Opus 5 | $0.00000 | $0.00083 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
xurl-api-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 4d 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
XURL API Probing
Probe APIs directly and methodically before assuming the client or app layer is at fault.
Use when
- An endpoint is failing and the transport details matter.
- The task needs a minimal repro using HTTP requests.
- You need to compare raw API behavior against app behavior.
Workflow
- Start with the smallest request that proves reachability and auth.
- Capture method, URL, headers, body, and the exact status code.
- Reduce payloads until the failure shape is obvious.
- Compare a passing and failing request whenever possible.
- Feed the findings back into the app fix or setup guidance.
Deliverable
- Minimal request examples.
- Exact response status and body shape.
- Root cause or likely boundary.
- Recommended app-side change or config fix.
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.
- 4d ago First seen · 22 lines · 0 tokens per session scan A 033c1d0984f7
xurl-api-probing is a skill published in the GitHub repository aaronnat23/disp8ch (99 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 166 tokens. 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
data-fetching
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, axios, React Query, SWR, error handling, caching strategies, offline support.
neuron-debugger
Debug and monitor Neuron AI applications with Inspector APM, event observability, logging, and performance analysis. Use this skill whenever the user mentions debugging, monitoring, observability, performance analysis, tracing, Inspector, or needs to understand why an agent is behaving a certain way. Also trigger for…
perf
Analyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.
api-debugging
Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
salesforce
Query and manage Salesforce CRM data via the Salesforce CLI (sf). Run SOQL/SOSL queries, inspect object schemas, create/update/delete records, bulk import/export, execute Apex, deploy metadata, and make raw REST API calls.
rest-graphql-debug
Debug REST/GraphQL APIs: status codes, auth, schemas, repro.