Borrowing it
Nothing to install: this file belongs to toonight/get-shit-done-for-antigravity. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/toonight/get-shit-done-for-antigravity/main/.agents/skills/plan-checker/SKILL.mdgit clone --depth 1 https://github.com/toonight/get-shit-done-for-antigravityWrote 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/toonight/get-shit-done-for-antigravity/plan-checker)<a href="https://agentmods.dev/skills/toonight/get-shit-done-for-antigravity/plan-checker"><img src="https://agentmods.dev/badge/skills/toonight/get-shit-done-for-antigravity/plan-checker/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/toonight/get-shit-done-for-antigravity/plan-checker"><img src="https://agentmods.dev/badge/skills/toonight/get-shit-done-for-antigravity/plan-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 40 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00013 | $0.01623 |
| Opus 5 | $0.00006 | $0.00812 |
| Sonnet 5 | $0.00003 | $0.00325 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade A, and why
plan-checker 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 12d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Plan Checker Agent
Your job: Find problems BEFORE execution, not during.
Validation Dimensions
Dimension 1: Requirement Coverage
Question: Does every phase requirement have task(s) addressing it?
Process:
- Extract phase goal from ROADMAP.md
- Decompose goal into requirements (what must be true)
- For each requirement, find covering task(s)
- Flag requirements with no coverage
Red flags:
- Requirement has zero tasks addressing it
- Multiple requirements share one vague task ("implement auth" for login, logout, session)
- Requirement partially covered
Example issue:
issue:
dimension: requirement_coverage
severity: blocker
description: "AUTH-02 (logout) has no covering task"
plan: "1-01"
fix_hint: "Add task for logout endpoint"
Dimension 2: Task Completeness
Question: Does every task have Files + Action + Verify + Done?
Required by task type:
| Type | Files | Action | Verify | Done |
|---|---|---|---|---|
auto |
Required | Required | Required | Required |
checkpoint:* |
N/A | N/A | N/A | N/A |
tdd |
Required | Behavior + Implementation | Test commands | Expected outcomes |
Red flags:
- Missing
<verify>— can't confirm completion - Missing
<done>— no acceptance criteria - Vague
<action>— "implement auth" instead of specific steps - Empty
<files>— what gets created?
Example issue:
issue:
dimension: task_completeness
severity: blocker
description: "Task 2 missing <verify> element"
plan: "1-01"
task: 2
fix_hint: "Add verification command"
Dimension 3: Dependency Correctness
Question: Are plan dependencies valid and acyclic?
Process:
- Parse
depends_onfrom each plan frontmatter - Build dependency graph
- Check for cycles, missing references, future references
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.
- 12d ago First seen · 284 lines · 13 tokens per session scan A 7248154cf4ce
plan-checker is a skill published in the GitHub repository toonight/get-shit-done-for-antigravity (947 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 1,623 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…