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-validatorgit 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-validator)<a href="https://agentmods.dev/skills/spielewoy/autoprompt-skill/ap-framework-validator"><img src="https://agentmods.dev/badge/skills/spielewoy/autoprompt-skill/ap-framework-validator.svg" alt="Measured on agentmods" 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.00764 |
| Opus 5 | $0.00046 | $0.00382 |
| Sonnet 5 | $0.00019 | $0.00153 |
| Haiku 4.5 | $0.00009 | $0.00076 |
Grade A, and why
ap-framework-validator 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 8d 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-validator - Level 4 (Terminal leaf - FRAMEWORK VALIDATE) 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 validation and write your ruling. You are TERMINAL - you do NOT spawn subagents, and you report a binary verdict up to the executor that spawned you. You saw NONE of the generator's reasoning; you judge the descriptor on its own evidence. You may run checks (Bash) and write your ruling (Write); you MUST NOT edit production code.
Your gate/function
FRAMEWORK VALIDATE (HRN-5 - default-FAIL): run the validateGeneratedFramework checklist from frameworks/generation.md §4 against the generated descriptor and confirm every check holds - a leaf is SOUND only if ALL pass, default toward FAIL on any doubt: (a) every gate ∈ GATE_LIBRARY (no unmapped gate); (b) exactly one terminal DONE scenario AND every negative scenario loops UP; (c) the BLOCKED INVARIANT present verbatim; (d) a non-empty acceptance set bound to a resolvable execharness. An unsound leaf is NEVER driven - return FAIL with the specific numbered reasons so the generator re-mints. A FAIL naming a real soundness breach is NOT arbitrable into PASS. Never wave through a leaf that lacks the BLOCKED invariant, lacks a terminal DONE, carries an unmapped gate, or has an empty acceptance set.
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.
- 8d ago First seen · 27 lines · 93 tokens per session scan A e17b72e74460
ap-framework-validator is a skill published in the GitHub repository Spielewoy/autoprompt-skill (1,008 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 764 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…
openrig-cmux
Use when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved view into live agent tiles via rig terminal --provider cmux, or driving cmux on an agent's request. Same OpenRig view semantics as openrig-herdr (the verbs, honest-partial/degrade, read-only cross-rig, scroll/copy…
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
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…
design-engineering
Apply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an…