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 commands/nguyenthienthanh/aura-frog/checkgit 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.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00524 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 4d 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 — 72 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. Produces scored report (0-100) with prioritized next steps.
Usage: /check, /check src/components
/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.
Usage: /check debt src/components --priority high
/check coverage
Test coverage analysis: statements, branches, functions, lines. Identifies files below target, uncovered lines, and suggests tests to write.
Usage: /check coverage --target 85
/check deps
Dependency vulnerability scan. Auto-detects package manager. Reports affected packages, fix versions, breaking change warnings. --fix for auto-resolution.
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.
- 4d ago First seen · 72 lines · 0 tokens per session scan A 5be5f0364eee
check is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 524 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
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.