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 commands/geoloeg-ist/agents-reverse-engineer/insert-phasegit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWhat 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.00024 | $0.01478 |
| Opus 5 | $0.00012 | $0.00739 |
| Sonnet 5 | $0.00005 | $0.00296 |
| Haiku 4.5 | $0.00002 | $0.00148 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gsd:insert-phase — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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> @.planning/ROADMAP.md @.planning/STATE.md </execution_context>
Example: /gsd:insert-phase 72 Fix critical auth bug
→ after = 72
→ description = "Fix critical auth bug"
Validation:
if [ $# -lt 2 ]; then
echo "ERROR: Both phase number and description required"
echo "Usage: /gsd:insert-phase <after> <description>"
echo "Example: /gsd:insert-phase 72 Fix critical auth bug"
exit 1
fi
Parse first argument as integer:
after_phase=$1
shift
description="$*"
# Validate after_phase is an integer
if ! [[ "$after_phase" =~ ^[0-9]+$ ]]; then
echo "ERROR: Phase number must be an integer"
exit 1
fi
if [ -f .planning/ROADMAP.md ]; then
ROADMAP=".planning/ROADMAP.md"
else
echo "ERROR: No roadmap found (.planning/ROADMAP.md)"
exit 1
fi
Read roadmap content for parsing.
-
Search for "### Phase {after_phase}:" heading
-
If not found:
ERROR: Phase {after_phase} not found in roadmap Available phases: [list phase numbers]Exit.
-
Verify phase is in current milestone (not completed/archived)
- Search for all "### Phase {after_phase}.N:" headings
- Extract decimal suffixes (e.g., for Phase 72: find 72.1, 72.2, 72.3)
- Find the highest decimal suffix
- Calculate next decimal: max + 1
Examples:
- Phase 72 with no decimals → next is 72.1
- Phase 72 with 72.1 → next is 72.2
- Phase 72 with 72.1, 72.2 → next is 72.3
Store as: decimal_phase="$(printf "%02d" $after_phase).${next_decimal}"
slug=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-//;s/-$//')
Phase directory name: {decimal-phase}-{slug}
Example: 06.1-fix-critical-auth-bug (phase 6 insertion)
phase_dir=".planning/phases/${decimal_phase}-${slug}"
mkdir -p "$phase_dir"
Confirm: "Created directory: $phase_dir"
-
Find insertion point: immediately after Phase {after_phase}'s content (before next phase heading or "---")
-
Insert new phase heading with (INSERTED) marker:
### Phase {decimal_phase}: {Description} (INSERTED) **Goal:** [Urgent work - to be planned] **Depends on:** Phase {after_phase} **Plans:** 0 plans Plans: - [ ] TBD (run /gsd:plan-phase {decimal_phase} to break down) **Details:** [To be added during planning] -
Write updated roadmap back to file
The "(INSERTED)" marker helps identify decimal phases as urgent insertions.
Preserve all other content exactly (formatting, spacing, other phases).
- Read
.planning/STATE.md - Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
- Phase {decimal_phase} inserted after Phase {after_phase}: {description} (URGENT)
If "Roadmap Evolution" section doesn't exist, create it.
Add note about insertion reason if appropriate.
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 · 228 lines · 24 tokens per session scan A cfab3ed5037d
gsd:insert-phase is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 25d ago), licensed MIT. It adds 24 tokens to every session and 1,478 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 commands, from other repositories
auto-reason
Subjective self-refinement with blind judging, Borda aggregation, and provider-agnostic model routing.
deep-research
Deep research — produce a cited decision-grade research report and artifact bundle.
goals
Goal-oriented mission entrypoint — set, view, or drive long-running objectives through the mission system.
launch-worker
Manually launch headless workers against one or more GitHub issues.
check-routines
Check and safely repair aidevops routine scheduler health.
local-permissions-check
Audit local host/runtime permissions for aidevops on macOS, Linux, Windows, and WSL.