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/acendas/shipyard/running-acceptance-probenpx skills add Acendas/shipyard --skill running-acceptance-probegit clone --depth 1 https://github.com/Acendas/shipyardWrote 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/acendas/shipyard/running-acceptance-probe)<a href="https://agentmods.dev/skills/acendas/shipyard/running-acceptance-probe"><img src="https://agentmods.dev/badge/skills/acendas/shipyard/running-acceptance-probe.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.1 | $0.00017 | $0.01999 |
| Opus 5 | $0.00009 | $0.01000 |
| Sonnet 5 | $0.00003 | $0.00400 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade B, and why
running-acceptance-probe 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 6d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| New API endpoint | `curl -fsS -X POST localhost:3000/api/users -d '{"name":"x"}' \| jq -e .id` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| New API endpoint | `curl -fsS -X POST localhost:3000/api/users -d '{"name":"x"}' \| jq -e .id` | How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running an Acceptance Probe
A probe is the smoke-test command that demonstrates a task's wiring works end-to-end — distinct from unit/integration tests, which assert behavior in isolation. The probe is the most important reliability artifact in Shipyard 2.0: it is the difference between "tests pass against a stub" and "the thing actually works."
What Counts as an Acceptance Probe
A valid probe is a single shell command that:
- Exits 0 on success. Non-zero exit means the wiring failed.
- Produces observable output that demonstrates the change worked end-to-end. Empty output passing is rare and suspicious.
- Runs from a clean state — no prerequisite session-only setup.
- Completes in a bounded time — typically <60s, hard cap 5m.
- Is deterministic enough to run twice and get the same exit code.
Examples of good probes (per task type):
| Task type | Probe shape |
|---|---|
| New API endpoint | curl -fsS -X POST localhost:3000/api/users -d '{"name":"x"}' | jq -e .id |
| New CLI subcommand | node bin/mytool.mjs <new-subcommand> --help | grep -q "<expected text>" |
| Library function | node -e 'const m = require("./dist/index.js"); if (!m.newFn) process.exit(1); console.log(m.newFn(42))' |
| Migration | psql -c "SELECT column_name FROM information_schema.columns WHERE table_name='users' AND column_name='new_col'" | grep -q new_col |
| Refactor (no behavior change) | npm run build && npm test -- --testPathPattern=touched-module |
| Frontend feature | a Playwright check, or curl -fsS localhost:3000/the-new-page | grep -q "<expected element>" |
Examples of bad probes:
npm test— that's a test suite, not a probe. Probes are narrower: they exercise this one feature's wiring.echo done— produces no observable evidence.cat <known-fixture>.json— doesn't exercise any new code.- An interactive command that needs user input.
- A command that depends on state from earlier in the session.
The probe is authored alongside acceptance criteria (see authoring-acceptance-probe). This skill is about running one that already exists.
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.
- 6d ago First seen · 142 lines · 17 tokens per session scan B 3a5a59381632
running-acceptance-probe is a skill published in the GitHub repository Acendas/shipyard (2 stars, last pushed 24d ago), licensed MIT. It adds 17 tokens to every session and 1,999 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tmux-real-user-testing
This skill should be used when the user asks to "用 tmux 做真实测试", "保存 tmux 日志", "像真实用户一样测试 Qwen", "生成可复查的 TUI 测试报告", "测试 slash command 交互", or requests a tmux-based real user E2E run with complete readable logs. It guides real TUI usage with step-by-step capture-pane snapshots rather than ANSI raw pipe logs.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
moai-ref-testing-pyramid
Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.
mailagent
Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
browser-qa
自动化视觉测试与 UI 交互验证。部署功能后使用浏览器自动化验证关键页面、核心路径和发布前回归。 当任务需要真实浏览器验证渲染、导航、交互或前端上线风险时使用。.