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/rules/duongductrong/antigravity-kit/coding-style)<a href="https://agentmods.dev/rules/duongductrong/antigravity-kit/coding-style"><img src="https://agentmods.dev/badge/rules/duongductrong/antigravity-kit/coding-style.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.1 | $0.00213 | $0.00213 |
| Opus 5 | $0.00106 | $0.00106 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
coding-style 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 3d 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:
- coding-style — 100% identical, 0 lines differ
What it actually says
- Type safety first: Prefer TypeScript with explicit types on public functions, props, and return values. Avoid any and implicit any.
- Guard clauses over nesting: Use early returns and guard clauses instead of deeply nested if/else blocks; keep branches short and readable.
- Use descriptive variable and function/const names. Also, event functions should be named with a "handle" prefix, like "handleClick" for onClick and "handleKeyDown" for onKeyDown.
- Clear naming & structure: Use descriptive, consistent names (camelCase for variables/functions, PascalCase for components) and keep related logic grouped in hooks/, utils/, components/.
- Avoid adding unnecessary comments to the code of your generated code.
- Small, pure units: Write small, single-purpose functions/components. Keep them pure when possible and move side effects (API calls, logging) to the edges.
- Refactor: Use the refactor command to improve the code quality without breaking existing functionality. Do not use it for simple code improvements.
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.
- 3d ago First seen · 12 lines · 213 tokens per session scan A cf6f46aa6edc
coding-style is a cursor rule published in the GitHub repository duongductrong/antigravity-kit (51 stars, last pushed 6mo ago), licensed MIT. It adds 213 tokens to every session, about $0.0011 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-09-03.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
modus-angular-button-group-usage-short
Critical patterns for ModusButton usage inside ModusButtonGroup in Angular.
release-checklist
What to update with each code change or version release.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.
smol-cli
Setup once per project: install with npm i -g @electrooo69/sped-cli@latest --force, then run sped setup --all in the project root if .sped-cli/ is missing. Never delete .sped-cli/. Only follow the instruction file for your current agent. Do not delete or modify other agents' instruction files unless explicitly asked.…
05-daemons-ipc
Use this rule to understand the roles of the HAPPE/IDA/mcp-hostd daemons, how HAPPE and IDA communicate via IPC, find the IPC message structure definitions, trace the memory retrieval flow, and identify daemon responsibilities.