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.
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/commands/nguyenthienthanh/aura-frog/check)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/check"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/check/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/commands/nguyenthienthanh/aura-frog/check"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/check.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.00000 | $0.00650 |
| Opus 5.5 | $0.00000 | $0.00260 |
| Sonnet 5.5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
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 27d 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Commands
Verify code quality, security, performance, and coverage. One command to audit everything.
Category: Verification Scope: Session
/check
Run all quality checks: lint, format, type check, coverage, complexity. (Code review is separate: /check review.) Produces scored report (0-100) with prioritized next steps.
Usage: /check, /check src/components
/check review
Evidence-based code review/audit of the current diff (default base main), a path, or a PR number, via skills/code-reviewer/SKILL.md: 8 aspects (security, correctness, compatibility, architecture, error handling, test gaps, type safety, simplicity). Each finding carries file:line + a concrete failure scenario; unproven findings are dropped. Ends with APPROVED / CHANGES REQUESTED.
Usage: /check review, /check review src/auth, /check review 123
/check security
Comprehensive security audit: dependency vulnerabilities (npm audit/pip-audit), secret detection (gitleaks), SAST (semgrep/eslint-security), OWASP Top 10 checks. Generates SECURITY_AUDIT.md with remediation plan.
Usage: /check security, /check security --quick (deps + secrets only)
/check perf
Performance analysis: Web (Lighthouse: FCP, LCP, TTI, CLS), Mobile (startup, memory), Backend (API response time, N+1), Bundle (size, chunks, duplicates). Scored 0-100 with prioritized recommendations.
For deep profiling of a specific bottleneck (not just surface metrics), delegate to skills/perf-profiling/SKILL.md — measure → analyze flamegraph → one change → verify.
Usage: /check perf, /check perf --bundle, /check perf --lighthouse
/check complexity
Cyclomatic + cognitive complexity analysis. Scale: 1-5 simple, 6-10 moderate, 11-20 complex, 21+ critical. Reports hotspots and refactoring priorities.
Usage: /check complexity src/services/auth.ts --threshold 10
/check debt
Technical debt tracking: TODO/FIXME/HACK, deprecated code, unused exports, duplication, code smells. Categorized by priority with effort estimates and remediation plans.
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.
- 27d ago Changed · +8 lines dcdbef3ee95e
- 1mo ago First seen · 72 lines · 0 tokens per session scan A 5be5f0364eee
check is a command published in the GitHub repository nguyenthienthanh/aura-frog (25 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 650 tokens. 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 commands, from other repositories
improve
/improve Scan and fix all improvement categories /improve arch Architectural improvements only /improve duplication Duplicate code / abstraction consolidation /improve quality Code quality (GuardLoop patterns GL-01 through GL-10) /improve security Security posture improvements /improve --dry-run Show what would be…
poly-check
Lint and check formatting with poly — apply no fixes; summarize findings and drift.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
tdd-bug
Fix a bug with regression test first.