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.
git clone --depth 1 https://github.com/YousefNabil-SOC/claude-apexWrote 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/yousefnabil-soc/claude-apex/execute-phase)<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/execute-phase"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/execute-phase/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/yousefnabil-soc/claude-apex/execute-phase"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/execute-phase.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.00017 | $0.00324 |
| Opus 5.5 | $0.00007 | $0.00130 |
| Sonnet 5.5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
gsd:execute-phase 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.
This is a copy
100% identical to gsd:execute-phase — 37 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.
What it actually says
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
Context budget: ~15% orchestrator, 100% fresh per subagent.
<execution_context>
@/.claude/get-shit-done/workflows/execute-phase.md
@/.claude/get-shit-done/references/ui-brand.md
</execution_context>
Flags:
--gaps-only— Execute only gap closure plans (plans withgap_closure: truein frontmatter). Use after verify-work creates fix plans.
Context files are resolved inside the workflow via gsd-tools init execute-phase and per-subagent <files_to_read> blocks.
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 · 42 lines · 17 tokens per session scan A 431239b9b6de
gsd:execute-phase is a command published in the GitHub repository YousefNabil-SOC/claude-apex (3 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 324 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to gsd:execute-phase, differing in 37 lines, and is treated as a copy.
Other commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
update-docs
Scan recently modified files and update the matching documentation.
handoff
Write a session handoff document for continuity.
optimize
Run the credo optimisation audit for the current repo: a freshness check, then a read-only scan (conflict hotspots, changelog fragments, test-stage convention, dogma settings, parallelism readiness, and - only if the user says Yes when asked before the scan - instruction consistency across the global and repo…
gws-tasks
List, create, complete, and manage Google Tasks.