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 kaeawc/auto-mobile --skill validategit clone --depth 1 https://github.com/kaeawc/auto-mobileWrote 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/kaeawc/auto-mobile/validate)<a href="https://agentmods.dev/skills/kaeawc/auto-mobile/validate"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/validate/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/kaeawc/auto-mobile/validate"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00454 |
| Opus 5.5 | $0.00014 | $0.00182 |
| Sonnet 5.5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
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 18d 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.sh --run-unit-lane, or pass an existing focused JUnit XML report to measure it directlybash 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.
- 18d ago Changed 176295c74a3c
- 2mo ago First seen · 41 lines · 34 tokens per session scan A 9f45b7d54b67
validate is a skill published in the GitHub repository kaeawc/auto-mobile (55 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 454 once invoked, about $0.0001 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-30.
validate compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| validatekaeawc/auto-mobile | Skill | 55 | today | Apache-2.0 | A | 34 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |