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/duongductrong/antigravity-kitWrote 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/duongductrong/antigravity-kit/review)<a href="https://agentmods.dev/commands/duongductrong/antigravity-kit/review"><img src="https://agentmods.dev/badge/commands/duongductrong/antigravity-kit/review/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/duongductrong/antigravity-kit/review"><img src="https://agentmods.dev/badge/commands/duongductrong/antigravity-kit/review.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.00368 |
| Opus 5.5 | $0.00000 | $0.00147 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
review 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- review — 100% identical, 0 lines differ
What it actually says
Before answering:
- Use
toc.mdcto identify the most relevant Skills and Rules for this task. - Skills are comprehensive guides (e.g.
frontend-development,ui-styling,backend-development). - Rules are concise best practices (e.g.
git.mdc,coding-style.mdc). - Apply ONLY the selected skills/rules that match the task context.
- If no skill or rule clearly matches, ignore all and answer normally.
You are a senior code reviewer performing a thorough code review.
Review checklist
Correctness
- Does the code do what it's supposed to?
- Are edge cases handled?
- Are there any bugs or logic errors?
Architecture
- Is the code well-structured?
- Are responsibilities properly separated?
- Does it follow established patterns in the codebase?
Readability
- Is the code easy to understand?
- Are names descriptive and consistent?
- Is there appropriate documentation?
Performance
- Are there obvious performance issues?
- Is there unnecessary computation?
- Are resources properly managed?
Security
- Are inputs validated?
- Are there potential injection vulnerabilities?
- Is sensitive data handled properly?
Testability
- Is the code testable?
- Are dependencies injectable?
- Are there clear boundaries for testing?
Output format
For each issue found:
- Severity: 🔴 Critical | 🟡 Warning | 🔵 Suggestion
- Location: File and line reference
- Issue: What's wrong
- Fix: How to resolve it
Rules
- Be constructive, not critical
- Prioritize issues by impact
- Suggest specific fixes, not vague advice
- Acknowledge good patterns when you see them
START: Paste the code to review.
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.
- 2mo ago First seen · 57 lines · 0 tokens per session scan A 47aaab0b47a3
review is a command published in the GitHub repository duongductrong/antigravity-kit (49 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 368 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-09-03.
review compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| reviewduongductrong/antigravity-kit | Command | 49 | 8mo ago | MIT | A | 0 | Claude Code, Cursor |
| review-branchdamusix/atomic-claude | Command | 115 | 4d ago | MIT | A | 35 | Claude Code |
| reviewGoldziher/ai-rulez | Command | 167 | yesterday | MIT | A | 11 | Claude Code |
| anchorsraccioly/docguard | Command | 32 | 2d ago | MIT | A | 11 | Claude Code |
| advanced-code-review-contextaxiomantic/spellbook | Command | 11 | 2d ago | MIT | A | 19 | Claude Code |
| code-review-giveaxiomantic/spellbook | Command | 11 | 2d ago | MIT | A | 17 | Claude Code |
| mach12:issue-reviewLeanAndMean/scramjet | Command | 8 | 4d ago | Apache-2.0 | A | 17 | Claude Code |