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/kaeawc/auto-mobile/validatenpx skills add kaeawc/auto-mobile --skill validategit clone --depth 1 https://github.com/kaeawc/auto-mobileWhat 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.00034 | $0.00435 |
| Opus 5 | $0.00017 | $0.00217 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
validate 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
Validate Changes
Run the lightest validation that covers the touched code, then widen only when needed.
- Prefer
validatefor multi-check verification. - Prefer
testwhen the request is specifically about running tests or reproducing a test failure. - Before inventing a validation command, check
scripts/andscripts/README.mdfor an existing validator.
Baseline Validation
bun run lintbun run buildbun run turbo:validatefor the local Turbo lint/build/test gate
Repo Script Validation
- Codex skills and
AGENTS.md:bash scripts/validate_codex_skills.sh - Fast multi-check pass:
bash scripts/all_fast_validate_checks.sh - Dockerfile:
bash scripts/hadolint/validate_hadolint.sh - GitHub Actions local runner setup:
bash scripts/act/validate_act.sh - Swift build:
bash scripts/ios/swift-build.sh - Swift format:
ONLY_TOUCHED_FILES=false bash scripts/swiftformat/validate_swiftformat.sh - Swift lint:
ONLY_TOUCHED_FILES=false bash scripts/swiftlint/validate_swiftlint.sh - Other useful validators:
bash scripts/validate-bun-test-timings.shbash scripts/detect-dead-code-ts.sh
Selection Rules
- TypeScript-only changes usually need
lint,build, and relevant tests. - Use
bun run turbo:*scripts instead of bareturbo ...; Turbo is installed locally and may not be on the shellPATH. - Shell or docs/config changes should prefer the matching script in
scripts/. - Android changes should use the Gradle wrapper from
android/. - iOS changes should use the existing
scripts/ios/entry points. - Write long validation output to
scratch/and report only the actionable failures.
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 · 41 lines · 34 tokens per session scan A 9f45b7d54b67
validate is a skill published in the GitHub repository kaeawc/auto-mobile (45 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 435 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-30.
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…