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 AdvancingTitans/agent-engineering-toolkit --skill aet-proofgit clone --depth 1 https://github.com/AdvancingTitans/agent-engineering-toolkitWrote 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/advancingtitans/agent-engineering-toolkit/aet-proof)<a href="https://agentmods.dev/skills/advancingtitans/agent-engineering-toolkit/aet-proof"><img src="https://agentmods.dev/badge/skills/advancingtitans/agent-engineering-toolkit/aet-proof/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/advancingtitans/agent-engineering-toolkit/aet-proof"><img src="https://agentmods.dev/badge/skills/advancingtitans/agent-engineering-toolkit/aet-proof.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.00041 | $0.00332 |
| Opus 5.5 | $0.00016 | $0.00133 |
| Sonnet 5.5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
aet-proof 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 2mo 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
/aet-proof
Answer one question: did this exact verification command run on this workspace?
Run:
aet quick proof --output <proof.json> \
[--relevant-path <path>] [--artifact <path>] -- <argv>
The user's explicit /aet-proof call authorizes writing the requested JSON
receipt. It does not authorize any other write. The host LLM may locate the
project's recommended command, smallest relevant test set, relevant paths, and
declared artifacts. The deterministic executor alone records argv, timestamps,
exit code, redacted log digests, Git/worktree binding, relevant file hashes,
environment binding, and artifacts.
Never describe an unexecuted or non-zero command as passed. Never reuse a historical result as a new execution. State that a bounded test does not prove the full test suite passed. Do not generate HTML, SVG, Viewer, or Evidence Pack.
Budget: command duration, at most one LLM call only when locating the command, zero remote calls by default, and one receipt write.
For a Chinese /aet-proof request, explain the receipt in natural Simplified
Chinese while keeping code and required technical terms in English. Otherwise
use English.
Write the one receipt, report its scope, and stop. Do not run additional tests or invoke Fresh unless the user explicitly requests them.
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.
- 2mo ago First seen · 37 lines · 41 tokens per session scan A 390b5b25779e
aet-proof is a skill published in the GitHub repository AdvancingTitans/agent-engineering-toolkit (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 332 once invoked, about $0.0002 per session on Opus 5.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
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
llm-as-judge-evaluation
Evaluate LLM outputs using frontier models as judges. Use for pairwise model comparison, quality scoring with custom rubrics, and automated evaluation pipelines. Covers position bias mitigation, statistical significance, and generating preference data for DPO/RLHF.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.