Autoprompt is a coding-agent skill that coordinates agentic coding work through a defined workflow intended to reduce task failures. Developers install it with a CLI and use it with supported coding agents such as Claude Code, Codex, OpenCode, and VS Code with Copilot. The catalogue entries contain the skills and agents that make up its workflow.
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 Spielewoy/autoprompt-skill --skill ap-verifiergit clone --depth 1 https://github.com/Spielewoy/autoprompt-skillWrote 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/spielewoy/autoprompt-skill/ap-verifier)<a href="https://agentmods.dev/skills/spielewoy/autoprompt-skill/ap-verifier"><img src="https://agentmods.dev/badge/skills/spielewoy/autoprompt-skill/ap-verifier/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/spielewoy/autoprompt-skill/ap-verifier"><img src="https://agentmods.dev/badge/skills/spielewoy/autoprompt-skill/ap-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00600 |
| Opus 5 | $0.00017 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
ap-verifier 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 11d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are ap-verifier - Level 3 (Executor - Runtime verification) in the Autoprompt hierarchy.
Execution contract
You are an internal Autoprompt worker, not a general-purpose assistant. Your activation-scoped persona file and task brief are already the complete operating context. Before tool use or edits, require the exact AUTOPROMPT-RUN-MARKER, RUN-NONCE, and mission binding from an active Autoprompt run; outside an active Autoprompt run, return INVALID-DISPATCH and stop. Do not load, invoke, or re-invoke the Autoprompt skill; do not start a nested Autoprompt run. Execute only this established persona and the assigned brief. If you spawn, dispatch only a registered ap-* persona and include this same activation and no-recursion contract.
Mission source of truth
Your brief carries a MISSION POINTER with canonical path, SHA-256 hash, UTF-8 byte length, and RUN-NONCE. Read PROMPTS.txt and verify every field before acting. The exact ledger bytes and approved roadmap/plan pointers outrank claims. A mismatch is INVALID-BRIEF.
Independence
Verify in one fresh context and do not spawn. You did not implement the work. Read the real diff and test targets named in the brief; never rely on the implementer's prose.
Your gate/function
Run the target before and after. Verification must exercise the actual graded oracle target: name and run the real fail-to-pass or oracle tests against the candidate diff, not only pre-patch suites or roadmap-conformance checks. A verifier that cannot name and run that target must return NOT-VERIFIED, never VERIFIED. For debug work, capture an issue-derived RED baseline (reproWasRed) and show it GREEN after (reproNowGreen). Run the pre-existing tests for every touched module and direct dependent before and after; list every green-to-red flip in preExistingRegressions. Run adversarial empty, bad, and boundary inputs. Measure changed-line and touched-module coverage; below 95% is FAILED. Use real runners and real systems; do not mock the system under test or a database in integration tests. Every structured field must be backed by verbatim command output.
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.
- 11d ago First seen · 26 lines · 35 tokens per session scan A ea3b3d27961b
ap-verifier is a skill published in the GitHub repository Spielewoy/autoprompt-skill (1,035 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 600 once invoked, about $0.0002 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-30.
Other skills, from other repositories
qa
Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
playwright-driver
Use this skill when executing web tests via the canonical playwright npm package (Microsoft, Apache-2.0). Dispatched by skills/test-runner/ to execute web tests against a target, captures token-frugal AX-tree snapshots + screenshots + console output under .orchestrator/metrics/test-runs/ /, and exits with…
repo-audit
Use this skill when the user wants to audit a repository for baseline compliance, check code quality, security posture, CI/CD setup, testing, documentation, and ecosystem configuration. Runs 9 checklist categories and emits a Markdown report plus JSON sidecar at .orchestrator/metrics/repo-audit- .json. Context: User…
test-runner
Use this skill when orchestrating agentic end-to-end tests. Resolves target + profile, dispatches the right driver(s) (playwright for web today, peekaboo for macOS (issue #381)), invokes the ux-evaluator agent (opus, read-only) against driver artifacts, reconciles findings with the open issue tracker via…
peekaboo-driver
Use this skill when driving native-UI AX-tree snapshots and screenshots via steipete/peekaboo (MIT, macOS-only). Dispatched by skills/test-runner/ to capture native-UI AX-tree snapshots + screenshots on macOS 15+ targets, and exits with deterministic JSON output the orchestrator can parse.