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 agentmods add skills/ourobx/agent-ebpf/testsprite-verifynpx skills add ourobx/agent-ebpf --skill testsprite-verifygit clone --depth 1 https://github.com/ourobx/agent-ebpfWrote 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/ourobx/agent-ebpf/testsprite-verify)<a href="https://agentmods.dev/skills/ourobx/agent-ebpf/testsprite-verify"><img src="https://agentmods.dev/badge/skills/ourobx/agent-ebpf/testsprite-verify.svg" alt="Measured on agentmods" 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 | $0.00105 | $0.06262 |
| Opus 5 | $0.00053 | $0.03131 |
| Sonnet 5 | $0.00021 | $0.01252 |
| Haiku 4.5 | $0.00011 | $0.00626 |
Grade A, and why
testsprite-verify scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
r = requests.post(f"{TARGET_URL}/login", json={"email": "[email protected]", "password": ""}) This is a copy
86% identical to testsprite-verify — 53 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestSprite Verification Loop
The verification loop that flies your just-shipped feature through the TestSprite CLI and reports back.
You just finished a piece of work in a TestSprite-tested repo. Before you report
it done, actually run the relevant TestSprite test(s) through the testsprite
CLI and read the result. Spec review and unit tests catch correctness; only
running the test catches what breaks for a real user.
When to run
Run after a feature or fix lands — one feature → one test run, at the moment it
lands, not batched at the end. Tests you create this way accumulate into the
project's TestSprite suite; before writing a new one, check testsprite test list
for an existing test that already covers the behavior and extend it instead of
duplicating.
The CLI tests a deployed URL — it doesn't build or host your environment.
Run the loop only once the change is live somewhere reachable (e.g. open the PR,
let CI deploy the preview/staging environment) and pass that URL as
--target-url. Running earlier verifies the previous build, not your change.
This CLI only tests a reachable deployed URL (it rejects localhost). If the change is only running locally and isn't deployed anywhere reachable yet:
- if the TestSprite MCP is available in this environment, hand off to it — it tunnels your local server and tests the running app;
- otherwise report the change as unverified-because-undeployed and stop — don't run against a stale deployment to manufacture a verdict.
If the user explicitly named a tool (the CLI or the MCP), honor that over this reachability heuristic.
When to skip
The skip list is narrow:
- Docs-only edits (
docs/**,*.md, comments). - Pure build/config edits (
tsconfig*, lint/prettier config, lockfile bumps with no behavior change). - This repo isn't actually wired to TestSprite (no project linked, no creds). Don't pull the user into a setup flow they didn't ask for — say so and stop.
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.
- 3d ago First seen · 493 lines · 105 tokens per session scan A 490ee19984e4
testsprite-verify is a skill published in the GitHub repository ourobx/agent-ebpf (1 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 6,262 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 86% identical to testsprite-verify, differing in 53 lines, and is treated as a copy.
Other skills, from other repositories
azure-network-ops
Azure cloud networking -- VNets, NSGs, ExpressRoute, VPN Gateways, Azure Firewalls, Load Balancers, Application Gateways, Route Tables, Network Watcher, Private Endpoints, DNS zones. Use when auditing Azure VNets, troubleshooting hybrid connectivity (ExpressRoute/VPN), checking NSG rules, inspecting firewall policies…
Network Security & Traffic Analysis
Network traffic analysis, PCAP parsing, IDS/IPS rule creation, firewall configuration auditing, and network anomaly detection.
unifi-wifi
Use when UniFi Wi-Fi is slow, unstable, or being tuned: "my wifi is slow but speedtest on the router is fast", "great signal, terrible speed", "should I use 80MHz or 40MHz", "channel planning", "co-channel interference", "DFS channels", "my APs keep picking the same channel", "audit my SSIDs", "hidden SSID", or…
unifi-connect
Use when connecting an agent to a UniFi gateway (UDM Pro, UDM SE, Cloud Gateway) for the first time, or when API calls to one are failing: empty response bodies, curl returning HTTP 000, 401 on a key that works elsewhere, "how do I get a UniFi API key", "SSH is closed on my UDM", "connect to UniFi", "talk to my UniFi…
unifi-clients
Use when operating on UniFi clients, devices, switch ports, or DHCP: "block a device", "kick a client off wifi", "restart an access point", "power cycle a PoE port", "move a device to a different VLAN", "my device is on the wrong subnet after I changed the port", "set a DHCP reservation", "change DHCP DNS servers"…
unifi-context-map
Use when an agent keeps guessing wrong about a UniFi network, when starting recurring agent work against a gateway, or when asked to "map my network", "document my UniFi setup", "build a network inventory", "what's on my network", "why does the agent keep using the wrong AP", or "audit my reservations against…