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 zeeshanhanif/agentic-sdlc-kit --skill acceptance-verificationgit clone --depth 1 https://github.com/zeeshanhanif/agentic-sdlc-kitWrote 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/zeeshanhanif/agentic-sdlc-kit/acceptance-verification)<a href="https://agentmods.dev/skills/zeeshanhanif/agentic-sdlc-kit/acceptance-verification"><img src="https://agentmods.dev/badge/skills/zeeshanhanif/agentic-sdlc-kit/acceptance-verification.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.00198 | $0.01696 |
| Opus 5 | $0.00099 | $0.00848 |
| Sonnet 5 | $0.00040 | $0.00339 |
| Haiku 4.5 | $0.00020 | $0.00170 |
Grade A, and why
acceptance-verification 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Verification
The independent check that turns developer-done into verified — the per-feature loop's real definition of done. Feature-implementation built and self-gated the feature; this skill audits it without the builder's investment. Auditor and mechanic stay separate: findings route (back to implementation as rework, or to the design's amendment path as defects) — this skill never fixes production code. The one thing it may correct is the measurement: test artifacts that fail its audit.
The fresh-eyes rule. Independence is this skill's entire value, and it is enforced through derivation, not session hygiene alone: every check is re-derived from the authoritative documents — technical-design §6's criteria, the FR/UC statements, the manifest — never from tasks.md's checkboxes, the implementation's delivery summary, or any session's claims of green. Those are the artifacts under audit, not evidence. Running in a fresh session is strongly recommended (and is how an orchestrator should invoke it), but the skill is not refused in-session — the derivation rule does the real work.
Inputs
Defaults; user paths win; source-gated citation throughout.
- The feature folder — technical-design.md (§6 acceptance criteria: the audit standard, §3 contracts, §8 escalations), ui-design.md, tasks.md (read only to confirm developer-done state — never as evidence of correctness).
- The sources behind the criteria — the SRS (verbatim FR statements and binding NFRs for this feature's trace) and use-cases.md (the flows, including alternates/exceptions). The criteria are audited against these too: a criterion that misencodes its FR is a finding, not an authority.
- The design manifest — the feature's screens: states coverage and conformance claims to spot-check.
- The live repo — the code, the test suites, the harness and its
commands (scaffold-notes / agent-instructions), the git history
(
FEAT-NNN T*commits and the feature's test-file diff). - The RTM —
docs/rtm.md(if present): Test ref is this skill's owned column, written on acceptance.
What ships with it
2 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.
- 7d ago First seen · 145 lines · 198 tokens per session scan A 9ff9f2b2bc12
acceptance-verification is a skill published in the GitHub repository zeeshanhanif/agentic-sdlc-kit (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 198 tokens to every session and 1,696 once invoked, about $0.0010 per session on Opus 5. 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-08-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.