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-framework-generatorgit 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-framework-generator)<a href="https://agentmods.dev/skills/spielewoy/autoprompt-skill/ap-framework-generator"><img src="https://agentmods.dev/badge/skills/spielewoy/autoprompt-skill/ap-framework-generator/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-framework-generator"><img src="https://agentmods.dev/badge/skills/spielewoy/autoprompt-skill/ap-framework-generator.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.00093 | $0.00836 |
| Opus 5 | $0.00046 | $0.00418 |
| Sonnet 5 | $0.00019 | $0.00167 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
ap-framework-generator 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 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.
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-framework-generator - Level 3 (Executor - FRAMEWORK GENERATE) 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: L3 - Executor
You do the real work directly: you generate the framework and write its artifact. You report a tight result up to the manager that dispatched you.
Your gate/function
FRAMEWORK GENERATE (HRN-4): on a SELECTOR FRAMEWORK: MISS, build a one-off custom framework for that exact task by following the algorithm in frameworks/generation.md. (1) classify the axes → the deliverable/acceptance/locus axes; (2) compose the gate sequence from the GATE-LIBRARY with the correct axis-specific verify gate (metric-threshold-verify/apply-dry-run/idempotent-replay/measure-first-baseline), never a meaningless unit-coverage-verify for a non-code shape; (3) emit the gen-<axis-signature> leaf DESCRIPTOR carrying the BLOCKED INVARIANT verbatim, S1-S5 scenarios (negatives loop UP, one terminal DONE), a bound execharness ref, and the mission's acceptance asks echoed into the leaf (HRN-8). Hand the descriptor to the ap-framework-validator (HRN-5) BEFORE any gate runs - an unsound leaf is NEVER driven; on FAIL re-mint ONCE, a second FAIL escalates OUT-OF-SCOPE. The generated leaf is a ONE-OFF (generation.md §5): validated, driven, then discarded - there is NO promotion registry, and an identical MISS later is simply GENERATED again. Never invent a gate outside the GATE-LIBRARY; never drive an unvalidated leaf.
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 · 27 lines · 93 tokens per session scan A 5d2b2b389bba
ap-framework-generator is a skill published in the GitHub repository Spielewoy/autoprompt-skill (1,019 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 836 once invoked, about $0.0005 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
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
agent-startup-and-context-ingestion
Use when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages, "rig context" surface. Covers the 4 failure modes that make startup context fail (old rig spec misses current operating mode; current agents…
vault-mirror
Use when you need to populate the Meta-Vault with machine-generated notes derived from session-orchestrator JSONL records. Converts entries from .orchestrator/metrics/sessions.jsonl and .orchestrator/metrics/learnings.jsonl into vault-conformant Markdown under 50-sessions/ and 40-learnings/. Called automatically at…
discovery
Use this skill when running systematic quality discovery and issue detection. Runs modular probes adapted to the project's tech stack, presents findings interactively for user triage, and creates VCS issues for confirmed problems. Invoked standalone via /discovery or embedded in session-end.
docs-orchestrator
Use this skill when orchestrating documentation generation and updates within a session. Maps session scope to audience-specific docs tasks (User / Dev / Vault), dispatches the docs-writer agent with source-grounded prompts, and reports coverage gaps to session-end. Gated on docs-orchestrator.enabled: true in Session…