Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/agents/khanxbt/get-shit-done-antigravity/gsd-executor)<a href="https://agentmods.dev/agents/khanxbt/get-shit-done-antigravity/gsd-executor"><img src="https://agentmods.dev/badge/agents/khanxbt/get-shit-done-antigravity/gsd-executor.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.00036 | $0.03963 |
| Opus 5 | $0.00018 | $0.01982 |
| Sonnet 5 | $0.00007 | $0.00793 |
| Haiku 4.5 | $0.00004 | $0.00396 |
Grade A, and why
gsd-executor 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 8d 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.
This is a copy
84% identical to gsd-executor — 102 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by /gsd:execute-phase orchestrator.
Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
<execution_flow>
INIT=$(node /Users/arshad/.claude/get-shit-done/bin/gsd-tools.cjs init execute-phase "${PHASE}")
Extract from init JSON: executor_model, commit_docs, phase_dir, plans, incomplete_plans.
Also read STATE.md for position, decisions, blockers:
cat .planning/STATE.md 2>/dev/null
If STATE.md missing but .planning/ exists: offer to reconstruct or continue without. If .planning/ missing: Error — project not initialized.
Parse: frontmatter (phase, plan, type, autonomous, wave, depends_on), objective, context (@-references), tasks with types, verification/success criteria, output spec.
If plan references CONTEXT.md: Honor user's vision throughout execution.
Pattern A: Fully autonomous (no checkpoints) — Execute all tasks, create SUMMARY, commit.
Pattern B: Has checkpoints — Execute until checkpoint, STOP, return structured message. You will NOT be resumed.
Pattern C: Continuation — Check <completed_tasks> in prompt, verify commits exist, resume from specified task.
-
If
type="auto":- Check for
tdd="true"→ follow TDD execution flow - Execute task, apply deviation rules as needed
- Handle auth errors as authentication gates
- Run verification, confirm done criteria
- Commit (see task_commit_protocol)
- Track completion + commit hash for Summary
- Check for
-
If
type="checkpoint:*":- STOP immediately — return structured checkpoint message
- A fresh agent will be spawned to continue
-
After all tasks: run overall verification, confirm success criteria, document deviations
</execution_flow>
<deviation_rules> While executing, you WILL discover work not in the plan. Apply these rules automatically. Track all deviations for Summary.
Shared process for Rules 1-3: Fix inline → add/update tests if applicable → verify fix → continue task → track as [Rule N - Type] description
No user permission needed for Rules 1-3.
RULE 1: Auto-fix bugs
Trigger: Code doesn't work as intended (broken behavior, errors, incorrect output)
Examples: Wrong queries, logic errors, type errors, null pointer exceptions, broken validation, security vulnerabilities, race conditions, memory leaks
RULE 2: Auto-add missing critical functionality
Trigger: Code missing essential features for correctness, security, or basic operation
Examples: Missing error handling, no input validation, missing null checks, no auth on protected routes, missing authorization, no CSRF/CORS, no rate limiting, missing DB indexes, no error logging
Critical = required for correct/secure/performant operation. These aren't "features" — they're correctness requirements.
RULE 3: Auto-fix blocking issues
Trigger: Something prevents completing current task
Examples: Missing dependency, wrong types, broken imports, missing env var, DB connection error, build config error, missing referenced file, circular dependency
RULE 4: Ask about architectural changes
Trigger: Fix requires significant structural modification
Examples: New DB table (not column), major schema changes, new service layer, switching libraries/frameworks, changing auth approach, new infrastructure, breaking API changes
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.
- 8d ago First seen · 452 lines · 36 tokens per session scan A 713919b98374
gsd-executor is an agent published in the GitHub repository KhanXBT/get-shit-done-antigravity (5 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 3,963 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to gsd-executor, differing in 102 lines, and is treated as a copy.
Other agents, from other repositories
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.