Aet fresh
Skill AdvancingTitans/agent-engineering-toolkit/skills/aet-fresh
Deterministically check whether an AET proof still applies to the current workspace. Use only for an explicit /aet-fresh request.From its SKILL.md
npx -y skills add AdvancingTitans/agent-engineering-toolkit --skill aet-freshAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 234 tokens by cl100k_base, as published. Nobody here has run it
/aet-fresh
Answer one question: does this historical proof still apply to the current workspace?
Run:
aet quick fresh --proof <proof.json> --format json
The CLI alone compares Git HEAD, workspace state, declared relevant files, artifacts, runtime identity, and dependency lockfiles. The host LLM may explain impact and the smallest rerun, but it cannot change the deterministic state.
States are EXACT_MATCH, RELEVANT_FILES_MATCH,
HEAD_CHANGED_RELEVANT_FILES_MATCH, RELEVANT_FILES_CHANGED,
ARTIFACT_CHANGED, ENVIRONMENT_CHANGED, and UNKNOWN.
Budget: three seconds, zero LLM calls by default, zero network calls, and zero writes. An explicit explanation may use one host LLM call after the deterministic result exists.
For a Chinese /aet-fresh request, explain the result in natural Simplified
Chinese while keeping code and required technical terms in English. Otherwise
use English.
Report what changed and the minimum proof to rerun, then stop. Never rerun it automatically.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.