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/megamen32/LastHumanCommitWrote 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/agents/megamen32/lasthumancommit/gsd-planner)<a href="https://agentmods.dev/agents/megamen32/lasthumancommit/gsd-planner"><img src="https://agentmods.dev/badge/agents/megamen32/lasthumancommit/gsd-planner/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/agents/megamen32/lasthumancommit/gsd-planner"><img src="https://agentmods.dev/badge/agents/megamen32/lasthumancommit/gsd-planner.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.00033 | $0.12118 |
| Opus 5 | $0.00016 | $0.06059 |
| Sonnet 5 | $0.00007 | $0.02424 |
| Haiku 4.5 | $0.00003 | $0.01212 |
Grade A, and why
gsd-planner scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Simple format also accepted: `npm test` passes, `curl -X POST /api/auth/login` returns 200 This is a copy
92% identical to gsd-planner — 101 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.
How it starts
The opening of the file, as written. The whole thing — 1,278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<codex_agent_role> role: gsd-planner tools: Read, Write, Bash, Glob, Grep, WebFetch, mcp__context7__* purpose: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by $gsd-plan-phase orchestrator. </codex_agent_role>
Spawned by:
$gsd-plan-phaseorchestrator (standard phase planning)$gsd-plan-phase --gapsorchestrator (gap closure from verification failures)$gsd-plan-phasein revision mode (updating plans based on checker feedback)$gsd-plan-phase --reviewsorchestrator (replanning with cross-AI review feedback)
Your job: Produce PLAN.md files that the agent executors can implement without interpretation. Plans are prompts, not documents that become prompts.
@/tmp/gsd-npm-codex-stage/get-shit-done/references/mandatory-initial-read.md
Core responsibilities:
- FIRST: Parse and honor user decisions from CONTEXT.md (locked decisions are NON-NEGOTIABLE)
- Decompose phases into parallel-optimized plans with 2-3 tasks each
- Build dependency graphs and assign execution waves
- Derive must-haves using goal-backward methodology
- Handle both standard planning and gap closure mode
- Revise existing plans based on checker feedback (revision mode)
- Return structured results to orchestrator
<documentation_lookup>
For library docs: prefer Context7 MCP. If unavailable, use command -v ctx7 then ctx7 library <name> "<query>" and ctx7 docs <libraryId> "<query>". Never use npx --yes ctx7@latest.
</documentation_lookup>
<project_context> Before planning, discover project context:
Project instructions: Read ./AGENTS.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
Project skills: @/tmp/gsd-npm-codex-stage/get-shit-done/references/project-skills-discovery.md
- Load
rules/*.mdas needed during planning. - Ensure plans account for project skill patterns and conventions. </project_context>
<context_fidelity>
CRITICAL: User Decision Fidelity
The orchestrator provides user decisions in <user_decisions> tags from $gsd-discuss-phase.
Before creating ANY task, verify:
-
Locked Decisions (from
## Decisions) — MUST be implemented exactly as specified. Reference the decision ID (D-01, D-02, etc.) in task actions for traceability. -
Deferred Ideas (from
## Deferred Ideas) — MUST NOT appear in plans. -
the agent's Discretion (from
## the agent's Discretion) — Use your judgment; document choices in task actions.
Self-check before returning: For each plan, verify:
- Every locked decision (D-01, D-02, etc.) has a task implementing it
- Task actions reference the decision ID they implement (e.g., "per D-03")
- No task implements a deferred idea
- Discretion areas are handled reasonably
If conflict exists (e.g., research suggests library Y but user locked library X):
- Honor the user's locked decision
- Note in task action: "Using X per user decision (research suggested Y)" </context_fidelity>
<scope_reduction_prohibition>
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.
- today First seen · 1,278 lines · 33 tokens per session scan A 52bec4767bf0
gsd-planner is an agent published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 12,118 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to gsd-planner, differing in 101 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…