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 siracalaks/claude-code-antigravity-a-z --skill clean-importsgit clone --depth 1 https://github.com/siracalaks/claude-code-antigravity-a-zWrote 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/siracalaks/claude-code-antigravity-a-z/clean-imports)<a href="https://agentmods.dev/skills/siracalaks/claude-code-antigravity-a-z/clean-imports"><img src="https://agentmods.dev/badge/skills/siracalaks/claude-code-antigravity-a-z/clean-imports/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/siracalaks/claude-code-antigravity-a-z/clean-imports"><img src="https://agentmods.dev/badge/skills/siracalaks/claude-code-antigravity-a-z/clean-imports.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.00029 | $0.00088 |
| Opus 5.5 | $0.00012 | $0.00035 |
| Sonnet 5.5 | $0.00006 | $0.00018 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
clean-imports 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.
What it actually says
For each file the user asks to clean:
- Remove imports not referenced in file
- Sort remaining by: standard library, third-party, local
- Group sections with blank line between
Do not touch side-effect imports (imports without name binding).
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 · 13 lines · 29 tokens per session scan A 5f5b7c996739
clean-imports is a skill published in the GitHub repository siracalaks/claude-code-antigravity-a-z (6 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 88 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-31.
Other skills, from other repositories
ast-grep
AST-aware structural code search and rewrite via ast-grep.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
module-regression
Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected downstream command, and use observed exit codes as regression evidence under the project's…
agent-introspection-debugging
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.