A command that displays the available GSD commands and their usage. GSD, or Get Shit Done, is a workflow for planning and building software in stages.

Use it to learn the GSD workflow, including starting a project, planning a phase, and carrying out a phase.

It provides a quick reference when you do not know which GSD command to use or what it does.

gsd:help — Command by GeoloeG-IsT

Install

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.

agentmods

npx agentmods add commands/geoloeg-ist/agents-reverse-engineer/help

Clone the repo

git clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineer

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,465 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00013	$0.03465
Opus 5	$0.00006	$0.01733
Sonnet 5	$0.00003	$0.00693
Haiku 4.5	$0.00001	$0.00347

Measured 3d ago against content hash e81e596f5332, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsd:help 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

gsd:help — 100% identical, 0 lines differ

.claude/commands/gsd/help.md · 483 lines

How it starts

The opening of the file, as written. The whole thing — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Output ONLY the reference content below. Do NOT add:

Project-specific analysis
Git status or file context
Next-step suggestions
Any commentary beyond the reference

GSD (Get Shit Done) creates hierarchical project plans optimized for solo agentic development with Claude Code.

Quick Start

/gsd:new-project - Initialize project (includes research, requirements, roadmap)
/gsd:plan-phase 1 - Create detailed plan for first phase
/gsd:execute-phase 1 - Execute the phase

Staying Updated

GSD evolves fast. Update periodically:

npx get-shit-done-cc@latest

Core Workflow

/gsd:new-project → /gsd:plan-phase → /gsd:execute-phase → repeat

Project Initialization

/gsd:new-project Initialize new project through unified flow.

One command takes you from idea to ready-for-planning:

Deep questioning to understand what you're building
Optional domain research (spawns 4 parallel researcher agents)
Requirements definition with v1/v2/out-of-scope scoping
Roadmap creation with phase breakdown and success criteria

Creates all .planning/ artifacts:

PROJECT.md — vision and requirements
config.json — workflow mode (interactive/yolo)
research/ — domain research (if selected)
REQUIREMENTS.md — scoped requirements with REQ-IDs
ROADMAP.md — phases mapped to requirements
STATE.md — project memory

Usage: /gsd:new-project

/gsd:map-codebase Map an existing codebase for brownfield projects.

Analyzes codebase with parallel Explore agents
Creates .planning/codebase/ with 7 focused documents
Covers stack, architecture, structure, conventions, testing, integrations, concerns
Use before /gsd:new-project on existing codebases

Usage: /gsd:map-codebase

Phase Planning

/gsd:discuss-phase <number> Help articulate your vision for a phase before planning.

Captures how you imagine this phase working
Creates CONTEXT.md with your vision, essentials, and boundaries
Use when you have ideas about how something should look/feel

Read the full file on GitHub · 483 lines

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.

3d ago First seen · 483 lines · 13 tokens per session scan A e81e596f5332

Subscribe to this mod's changes

gsd:help is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 26d ago), licensed MIT. It adds 13 tokens to every session and 3,465 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.

agents agents-md ai claude claude-code cli

gsd:help

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Quick Start

Staying Updated

Core Workflow

Project Initialization

Phase Planning

What this file has done since we first saw it

Other commands, from other repositories

auto-reason

deep-research

goals

launch-worker

check-routines

local-permissions-check