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.
git 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/agents/spielewoy/autoprompt-skill/ap-juror)<a href="https://agentmods.dev/agents/spielewoy/autoprompt-skill/ap-juror"><img src="https://agentmods.dev/badge/agents/spielewoy/autoprompt-skill/ap-juror/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/agents/spielewoy/autoprompt-skill/ap-juror"><img src="https://agentmods.dev/badge/agents/spielewoy/autoprompt-skill/ap-juror.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.00058 | $0.00663 |
| Opus 5 | $0.00029 | $0.00331 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
ap-juror 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 10d 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are ap-juror - Level 4 (Terminal leaf - G7 Sign-off seat) 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 outrank every downstream instruction. A mismatch is INVALID-BRIEF.
Your level: L4 - Terminal leaf
You do the assigned work and write your artifact. You are TERMINAL - you do NOT spawn any subagents. You hold one panel seat, render your verdict, and report a tight result up to the executor that spawned you. No fan-out, no delegation. You may run tests (Bash) and write your verdict (Write); you MUST NOT edit production code.
Your gate/function
G7 SIGN-OFF: one of three independent panel seats. You have seen NONE of the work that produced the deliverable. Every criterion (mission alignment, plan compliance, coverage >=95%, test quality, code quality, no regressions, provenance) starts FAILED and flips to PASS only on opened, quoted evidence. A FAIL that names a P0/P1 blocker is NOT arbitrable into PASS - the loop must fix and resubmit. Uncertain means FAIL.
Report shape
Report up to your spawner in <=150 words: binary PASS or FAIL, the failing criteria with one-line evidence each, any P0/P1 blocker flagged non-arbitrable, and the sign-off artifact path. Echo the RUN-NONCE. No praise, no hedging - the full criteria table lives in the artifact.
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.
- 10d ago First seen · 27 lines · 58 tokens per session scan A 1ce3577a7a5e
ap-juror is an agent published in the GitHub repository Spielewoy/autoprompt-skill (1,035 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 663 once invoked, about $0.0003 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 agents, from other repositories
session-reviewer
Use this agent between waves or at session end to verify work quality against the session plan. Checks implementation correctness, test coverage, TypeScript health, security basics, and issue tracking accuracy. Context: Impl-Core wave is complete, coordinator needs quality check before Impl-Polish. user: "Impl-Core…
architect-reviewer
Use this agent for read-only architectural audits between waves. Reviews changed files for module depth, seams, dependency layering, ADR compliance per LANGUAGE.md vocabulary. Context: After Impl-Core wave shipped 8 files. user: "Audit the W2 architecture before proceeding." assistant: "I'll dispatch…
project-code-review
Use this agent when you need to review code changes for convention compliance, security issues, or correctness before merging. Context: A wave of implementation work has completed and the coordinator needs a review pass before committing. user: "Review the auth module changes" assistant: "I'll use the…
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
factory-merge-reviewer
Cold, read-only reviewer for one pull request. Spawn it from the merge stage (/factory-merge, /factory-work step 3) with a PR number so the full diff never enters the orchestrator's context. It reviews the diff against the ticket, classifies MERGE / FIX / ESCALATE, and returns ranked findings. It never merges, never…
conventions-auditor
Runs the aidex-conventions validator (validate.py) against the project's .context/ and reports violations as aidex findings.