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/insert-phase)<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/insert-phase"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/insert-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/insert-phase"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/insert-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.00024 | $0.00245 |
| Opus 5.5 | $0.00010 | $0.00098 |
| Sonnet 5.5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
gsd:insert-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:insert-phase — 4 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
Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions.
Purpose: Handle urgent work discovered during execution without renumbering entire roadmap.
<execution_context> @~/.claude/get-shit-done/workflows/insert-phase.md </execution_context>
Roadmap and state are resolved in-workflow via init phase-op and targeted tool calls.
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 · 33 lines · 24 tokens per session scan A dfff68e01563
gsd:insert-phase is a command published in the GitHub repository YousefNabil-SOC/claude-apex (3 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 245 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:insert-phase, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
golden-path
The golden path. One command, idea to merged PR. Runs the full pipeline, prd → prp → plan → dev → test → pr, with sensor + eval gates at every stage.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.