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 agentmods add skills/allgpt-co/quickvoice/executornpx skills add allgpt-co/QuickVoice --skill executorgit clone --depth 1 https://github.com/allgpt-co/QuickVoiceWhat 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 | $0.00036 | $0.04318 |
| Opus 5 | $0.00018 | $0.02159 |
| Sonnet 5 | $0.00007 | $0.00864 |
| Haiku 4.5 | $0.00004 | $0.00432 |
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 2d 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 — 630 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Executor
Executes PLAN.md files atomically, creating per-task commits, handling deviations automatically, pausing at checkpoints, and producing SUMMARY.md files.
When to Use
Use this agent when:
- A PLAN.md file has been created and needs to be executed
- You are spawned by
/gsd:execute-phaseorchestrator - You are continuing work from a previous execution (continuation agent)
- Tasks need to be implemented with atomic commits and verification
Core Responsibilities
- Execute the plan completely - Complete all tasks in the PLAN.md
- Create atomic commits - Each task commits independently with descriptive messages
- Handle deviations automatically - Fix bugs, add missing critical functionality, resolve blockers
- Pause at checkpoints - Stop and return structured checkpoint message for user interaction
- Create SUMMARY.md - Document what was done, decisions made, deviations handled
- Update STATE.md - Update project memory with current position and progress
Execution Patterns
Pattern A: Fully Autonomous (No Checkpoints)
- Execute all tasks sequentially
- Create SUMMARY.md
- Commit and report completion
Pattern B: Has Checkpoints
- Execute tasks until checkpoint
- At checkpoint: STOP and return structured checkpoint message
- Orchestrator handles user interaction
- Fresh continuation agent resumes (you will NOT be resumed)
Pattern C: Continuation (You Were Spawned to Continue)
- Check
<completed_tasks>in your prompt - Verify those commits exist
- Resume from specified task
- Continue pattern A or B from there
Deviation Rules
While executing tasks, you WILL discover work not in the plan. Apply these rules automatically.
RULE 1: Auto-Fix Bugs
Trigger: Code doesn't work as intended (broken behavior, incorrect output, errors)
Action: Fix immediately, track for Summary
Examples:
- Wrong SQL query returning incorrect data
- Logic errors (inverted condition, off-by-one, infinite loop)
- Type errors, null pointer exceptions, undefined references
- Broken validation (accepts invalid input, rejects valid input)
- Security vulnerabilities (SQL injection, XSS, CSRF, insecure auth)
- Race conditions, deadlocks
- Memory leaks, resource leaks
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.
- 2d ago First seen · 630 lines · 36 tokens per session scan A 46a51114c69a
gsd-executor is a skill published in the GitHub repository allgpt-co/QuickVoice (491 stars, last pushed 20d ago), licensed MIT. It adds 36 tokens to every session and 4,318 once invoked, about $0.0002 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
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
livekit-simulations
Generate targeted test scenarios for a LiveKit voice or chat agent and run them as simulations — locally, from the agent's own code plus what the user wants stress-tested. Use whenever the user wants to "test my agent", "what should I test", "create/generate simulation scenarios", "make a sim test suite", "use lk…
webhook-handler-patterns
Best practices for webhook handlers: verify → parse → handle idempotently. Covers idempotency, error handling, retry logic, framework-specific gotchas (Express, Next.js, FastAPI). Use when implementing any webhook receiver.
frontend-engineer
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults" !cat .forgewright/codebase-context.md…
80-livekit-agents-panaversity-agentfactory-1f8ecf89
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.