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/10Legs/freelance-developer-harnessWrote 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/10legs/freelance-developer-harness/retro)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/retro"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/retro/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/10legs/freelance-developer-harness/retro"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/retro.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.00009 | $0.00737 |
| Opus 5.5 | $0.00004 | $0.00295 |
| Sonnet 5.5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
retro 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are facilitating a Retrospective for: $ARGUMENTS
Where this retro lives
Per-project sprint tracking convention (see CLAUDE.md → Multi-Client Governance).
The retro lives inside the sprint file, not in a separate document.
The active sprint is found via the CURRENT symlink:
clients/{{CLIENT_SLUG}}/projects/{{PROJECT_SLUG}}/sprints/CURRENT
-> sprint-NNN.md
Step 0: Resolve the active sprint
-
Read
CLIENT_SLUGandPROJECT_SLUGfrom the active client lock (.claude/sessions/<SESSION_ID>.client). If none, stop and ask the user to run/use-client <slug> <project>first. -
Set
SPRINTS_DIR=clients/<CLIENT_SLUG>/projects/<PROJECT_SLUG>/sprintsandACTIVE=$SPRINTS_DIR/CURRENT. -
Verify
$ACTIVEexists and is a symlink:[ -L "$ACTIVE" ] || { echo "no active sprint — run /sprint-plan first"; exit 1; } ACTIVE_FILE=$(readlink "$ACTIVE") # e.g. sprint-007.md ACTIVE_PATH="$SPRINTS_DIR/$ACTIVE_FILE" -
Confirm the sprint is
status: activein its frontmatter. If it is alreadyclosed, ask the user whether to reopen or to start a new sprint via/sprint-plan.
Retrospective Format
1. What Went Well? (Preserve)
Each council reflects:
- Creative Council
- Technical Council
- Hardware Council (hardware/hybrid projects only)
- Delivery Council
2. What Didn't Go Well? (Improve)
Each council reflects: friction, delays, rework, broken communication.
3. What Did We Learn?
- New patterns worth capturing in
patterns/ - Process updates worth keeping
- Client-specific insights worth documenting
4. Action Items
For each "didn't go well" item:
- Specific action
- Owner
- Target date
- Done-when criterion
5. Patterns Library Update
Based on learnings: what should be added, updated, or removed from patterns/.
Output — write the retro back into the sprint file
- Edit
$ACTIVE_PATHin place:- Set frontmatter
status: closed - Set frontmatter
closed_date: <today, YYYY-MM-DD> - Fill in the
## Retrospectivesection with all five subsections above
- Set frontmatter
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.
- 5d ago First seen · 91 lines · 9 tokens per session scan A 6a5c13bc8223
retro is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 737 once invoked, about $0.0000 per session on Opus 5.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-10-02.
Other commands, from other repositories
dashboard
Starts the live web dashboard for the current fellowship — quest/scout progress, gate approvals, and event history — in the background, and prints the URL.
mega-status
Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.
hybrid-status
Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.
issues-setup
Set up issue tracker integration (Linear, Jira, or GitHub Issues) via MCP.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
hybrid-complete
Complete Hybrid Ralph task in worktree, verify all stories complete, commit code changes (excluding planning files), merge to target branch, and cleanup worktree directory. Can be run from any directory.