Borrowing it
Nothing to install: this file belongs to boringcomputers/nehemiah. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/boringcomputers/nehemiah/main/.agents/skills/testing-preview/SKILL.mdgit clone --depth 1 https://github.com/boringcomputers/nehemiahWrote 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/boringcomputers/nehemiah/testing-preview)<a href="https://agentmods.dev/skills/boringcomputers/nehemiah/testing-preview"><img src="https://agentmods.dev/badge/skills/boringcomputers/nehemiah/testing-preview/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/boringcomputers/nehemiah/testing-preview"><img src="https://agentmods.dev/badge/skills/boringcomputers/nehemiah/testing-preview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 58 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Privilege Escalation · line 26 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Data Exfiltration · line 29 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00032 | $0.00913 |
| Opus 5.5 | $0.00013 | $0.00365 |
| Sonnet 5.5 | $0.00006 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade B, and why
testing-preview scanned grade B with 2 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 2mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo NEHEMIAH_NET=1 NEHEMIAH_JAILER=0 NEHEMIAH_TOKEN=test-token /tmp/nehemiahd & Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8080/v1/machines -X POST \ How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing the Preview Feature
What It Does
The preview proxy exposes a port running inside a guest Firecracker VM at a public URL. Two implementations exist:
- Path-based (
/v1/machines/{id}/web/{port}/{path...}) — works over SSH tunnel and without wildcard DNS - Subdomain-based (
<id>--<port>.<PreviewBase>) — requires Caddy on-demand TLS + wildcard DNS
Prerequisites
- nehemiahd must be running with
NEHEMIAH_NET=1(enables guest networking via tap/bridge/DHCP) - A test VM must be created with
net: true(ensures DHCP lease is assigned) - An HTTP server must be running inside the guest on a known port
How to Set Up a Test VM
# Build and run nehemiahd (with auth to test the auth bypass)
cd nehemiahd && go build -o /tmp/nehemiahd .
sudo NEHEMIAH_NET=1 NEHEMIAH_JAILER=0 NEHEMIAH_TOKEN=test-token /tmp/nehemiahd &
# Create a VM with networking
curl -s http://localhost:8080/v1/machines -X POST \
-H "Authorization: Bearer test-token" \
-d '{"template":"python","ttl_seconds":900,"net":true}'
# Start an HTTP server inside the guest (via WebSocket TTY)
python3 -c "
import websocket, time
ws = websocket.create_connection('ws://localhost:8080/v1/machines/MACHINE_ID/tty',
header=['Authorization: Bearer test-token'])
time.sleep(0.5)
ws.send(b'cd / && python3 -m http.server 8000 --bind 0.0.0.0 &\n')
time.sleep(2)
ws.close()
"
Key Test Cases
The server above is started from / (cd /), so http.server serves the guest's
root filesystem — that makes the sub-path test below resolve.
- Preview without auth:
curl http://localhost:8080/v1/machines/{id}/web/8000/should return content (the/directory listing; no auth header needed) - Other routes still require auth:
curl http://localhost:8080/v1/machines/{id}should return 401 - Sub-path routing:
curl http://localhost:8080/v1/machines/{id}/web/8000/etc/should show the guest's/etcdirectory listing (proves sub-paths are proxied through) - Via Vite proxy:
curl http://localhost:5173/boring/v1/machines/{id}/web/8000/should work
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.
- 2mo ago First seen · 72 lines · 32 tokens per session scan B 5c6dcac1a722
testing-preview is a skill published in the GitHub repository boringcomputers/nehemiah (344 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 913 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gstack-qa
QA lead with real browser testing. Tests your app, finds bugs, fixes them with atomic commits, generates regression tests. Use when the user says "QA", "test this", "find bugs", "exploratory test", "QA this", or "test the app".
basic-browser-setup
Set up browser QA in AgentWorks, save verified locators and application knowledge, configure a repeatable smoke test, and establish reporting. Use when onboarding an application or repairing its QA foundation.
e2e-tester
Test a web app like a QA person — open it in a real browser, click through flows, and report what's broken with screenshots and code references. Works on localhost. Use when the user wants to test their app, verify a flow works, check for visual bugs, or validate changes before pushing.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.