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 agentmods add skills/aawwcc/ape/overridenpx skills add AAWWCC/ape --skill overridegit clone --depth 1 https://github.com/AAWWCC/apeWrote 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/aawwcc/ape/override)<a href="https://agentmods.dev/skills/aawwcc/ape/override"><img src="https://agentmods.dev/badge/skills/aawwcc/ape/override.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.00014 | $0.00274 |
| Opus 5 | $0.00007 | $0.00137 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
override 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 5d 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.
What it actually says
APE override
Use only when the user explicitly requests an abort or reset. Require a non-empty audit reason; ask
for it before calling when absent.
On Google Antigravity / Gemini, pass the exact open project root as project_dir on both the status
check and the override call.
Call ape_run with action: "override", operation abort or reset, the reason, and an optional
run-ID confirmation. After a conversational gap or when the user names a run, call
ape_status first and pass the returned run_id; a mismatch must fail closed. Do not invent a
run ID or retry an aimed operation as unaimed without user direction.
reset is valid only for terminal or blocked runs. For a running orphaned dispatch, use
expire-dispatch with its ticket ID and an audit reason. For a run held because automatic merge is
disabled, use ship with an audit reason. Override never makes evidence green, bypasses receipt
validation, skips tests, or bypasses merge gates.
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.
- 5d ago First seen · 24 lines · 14 tokens per session scan A 7d77840138a4
override is a skill published in the GitHub repository AAWWCC/ape (0 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 274 once invoked, about $0.0001 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
agent-orchestrator-v2
Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and…
self-improvement
Captures lessons and promotes recurring patterns.
plan-before-code
Plans multi-step work before writing code.
brainstorming
Refines rough ideas into approved designs before code.
code-review
Reviews diffs by severity to produce actionable feedback.
codebase-onboarding
Maps an unfamiliar repo before touching its code.