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/advancingtitans/agent-engineering-toolkit/aet-checknpx skills add AdvancingTitans/agent-engineering-toolkit --skill aet-checkgit clone --depth 1 https://github.com/AdvancingTitans/agent-engineering-toolkitWhat 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 | $0.00043 | $0.00411 |
| Opus 5 | $0.00022 | $0.00205 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
aet-check 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 2d 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-check
Answer one question: are this repository's Agent engineering assets usable and honest about verification?
Boundary
- Start with
aet quick check <root> --format json. - Read only Agent instructions, Skills, README, package/test configuration, CI, and files directly relevant to the finding.
- Do not read complete Git history, execute project code, access credentials, write files, or call remote tools by default.
- The deterministic preflight owns
PASS,FAIL,UNKNOWN, andNOT_APPLICABLE. Never rewrite them.
Investigation
The host LLM may form at most three competing hypotheses and use authorized
tools to clarify project-specific meaning. Every factual claim needs a
hash-bound result_ref; inspect a reasonable counter-explanation before
issuing SUPPORTED. Preserve the distinction between facts, engineering
judgment, uncertainty, and suggested action.
Before rendering an Investigated Finding, pass the canonical Finding, Ledger,
authorized-tool set, and Investigation Contract through
aet.investigation.validate_investigated_finding. If that API is unavailable
or rejects the record, preserve HYPOTHESIS/UNKNOWN and disclose why.
Budget: 30 seconds, three rounds, at most two LLM calls, six tool calls, one expensive call, zero remote calls, and five reported findings.
If the user invoked /aet-check in Chinese and asked in Chinese, explain the
result in natural Simplified Chinese while keeping code and required technical
terms in English. Otherwise use English.
Emit the bounded report, disclose uninspected surfaces, and stop. Do not start Scope, Proof, Fresh, Learn, Gate, Stage, Adopt, or a repair.
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.
- 2d ago First seen · 43 lines · 43 tokens per session scan A 8061a680635c
aet-check is a skill published in the GitHub repository AdvancingTitans/agent-engineering-toolkit (2 stars, last pushed 25d ago), licensed MIT. It adds 43 tokens to every session and 411 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…