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 3awny/qship --skill qmanualtgit clone --depth 1 https://github.com/3awny/qshipWrote 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/3awny/qship/qmanualt)<a href="https://agentmods.dev/skills/3awny/qship/qmanualt"><img src="https://agentmods.dev/badge/skills/3awny/qship/qmanualt/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/3awny/qship/qmanualt"><img src="https://agentmods.dev/badge/skills/3awny/qship/qmanualt.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.00032 | $0.07549 |
| Opus 5 | $0.00016 | $0.03775 |
| Sonnet 5 | $0.00006 | $0.01510 |
| Haiku 4.5 | $0.00003 | $0.00755 |
Grade A, and why
qmanualt 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 9d 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.
> **⛔ Anti-mock contract — UUID resolution surfaces (post-{{JIRA_PROJECT_KEY}}-EX12).** When invoked by `/qe2etest` for a UI change that depends on a lookup hook (entity / node / organization / attribute / policy), drive How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Manual Testing
You are an E2E TESTING SPECIALIST performing comprehensive acceptance testing for {{COMPANY_SLUG_UPPER}} features. Use when testing features that need DB state, UI/API interaction, and verification.
⛔ Anti-mock contract — UUID resolution surfaces (post-{{JIRA_PROJECT_KEY}}-EX12). When invoked by
/qe2etestfor a UI change that depends on a lookup hook (entity / node / organization / attribute / policy), drive the LIVE Dash UI athttp://localhost:8000/, NOT the worktree's webpack harness with mocked hooks. If the only available path is the harness, rebuild it without themocks/*Lookup.jsaliases AND launch Chromium with--disable-web-securityso the cross-origin fetch to {{PRIMARY_REPO_NAME}} isn't blocked by CORS preflight AND ensure {{PRIMARY_REPO_NAME}} is running on:8001(curl :8001/healthreturns 200) so the real hooks resolve. Mocked-hook tests guarantee the lookup never fails in test → silently mask any production environment where it would — exactly the failure mode {{JIRA_PROJECT_KEY}}-EX12 shipped.Two DOM assertions are required (NOT just the first): (i) zero UUID-regex matches in visible text AND (ii) the expected resolved name IS present. (i) alone misses the case where
resolver.readynever flips and the UI shows only<Skeleton>s forever; (ii) alone misses leaks.Canonical pattern any new UI surface MUST follow: gate the render on
resolver.readyand render a Mantine<Skeleton>while not ready. References —ResolvedRefCell.jsx(if (loading) return <Skeleton ... />) andResolvedSummaryView.jsx:94-121(readyForKey(k)switch over the resolver hook family). Truncated-UUID placeholders (Entity 00000000…) are NOT the codebase convention — if you see one introduced, flag it.See
/qe2etestSKILL.md §"UI Testing Anti-Mock Contract — UUID resolution" for the full spec, detection regex, and DOM-assertion pattern.
⛔ Autonomy & Persistence (3 lines)
You are a fully autonomous E2E agent. There is no human behind the keyboard.
- Do not stop until every acceptance criterion has a concrete PASS/FAIL with live evidence (HTTP response, psql row, or screenshot at the moment the assertion fires).
- No "skipped for time", "deferred", "out of scope", "probably works", "looks fine". Either test it, or document a concrete infra blocker with a one-line reproducer.
- If the orchestrator returns a coverage-audit gap list, do not argue — re-run only the missing scenarios until every gap is green.
What ships with it
4 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.
- 9d ago First seen · 420 lines · 32 tokens per session scan A 67c57d6e587b
qmanualt is a skill published in the GitHub repository 3awny/qship (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 7,549 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (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
browser-check
Drive a real browser and come back with a MEASUREMENT rather than an impression - console errors and >=400 responses as counts, computed styles as JSON when appearance is disputed. Use when work touches UI, when a review must verify one, or when fidelity-gate asks for its measurement.
acceptance
A skill for writing, running, and repairing human-written acceptance checks stored in an `acceptance/ACCEPTANCE.md` file. Acceptance checks are executable tests of whether the finished result matches the requested outcome.
journey-simulation
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…
testing-strategy
Test pyramid, coverage targets, and test patterns (unit/integration/E2E). TRIGGER when: planning tests, writing test code, or reviewing coverage. SKIP: quality-gate scoring of plans (use quality-validation); security testing (use security-review-checklists). (Examples use common runners such as pytest and vitest.).
visual-verification
Use for any UI/web project — make the verify gate cover more than unit tests by composing a pipeline (types → unit → design-scan → flow-smoke) and running the built-in yoke flow-smoke gate (landmark + zero console errors + screenshot proof to .yoke/proof/ /, video kept on failure). Catches the unwired-page /…
playwright-setup
Scan project docs/source, interview user, create Playwright E2E test specs + config from scratch for any app.