Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add limeflash/antigravity-plugin-cc/plugin install agyWrote 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/limeflash/antigravity-plugin-cc/status)<a href="https://agentmods.dev/commands/limeflash/antigravity-plugin-cc/status"><img src="https://agentmods.dev/badge/commands/limeflash/antigravity-plugin-cc/status/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/limeflash/antigravity-plugin-cc/status"><img src="https://agentmods.dev/badge/commands/limeflash/antigravity-plugin-cc/status.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.00020 | $0.00320 |
| Opus 5.5 | $0.00008 | $0.00128 |
| Sonnet 5.5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
status 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 1mo 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
List recent agy jobs (no argument) or show the detail block for a single job (when an id or prefix is provided).
How to invoke
The user's request:
$ARGUMENTS
If $ARGUMENTS is empty, run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" status
If $ARGUMENTS contains a job id (full agy-xxxxxxxx) or a unique
prefix (agy-3a7b), pass it through as the first positional
argument:
node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" status "<id-or-prefix>"
Behavior notes
- Jobs are stored per repository under
<repo>/.agy-plugin/jobs/. Running/agy:statusfrom outside the repo where you started a job will not show it — that's intentional. - The companion treats
runningrecords whose PID is dead asfailedin the rendered output (without rewriting the record). If you see a downgrade note in the detail block, the worker process is gone but the on-disk record didn't get the update. - Ambiguous prefixes exit 2 and list candidates so the user can pick a longer prefix.
Return the companion's stdout verbatim.
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.
- 1mo ago First seen · 45 lines · 20 tokens per session scan A 74f9fb19ccf6
status is a command published in the GitHub repository limeflash/antigravity-plugin-cc (2 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 320 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.