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/sprint-plan)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/sprint-plan"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/sprint-plan/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/sprint-plan"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/sprint-plan.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.00022 | $0.00985 |
| Opus 5.5 | $0.00009 | $0.00394 |
| Sonnet 5.5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
sprint-plan 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running Sprint Planning for: $ARGUMENTS
Where this sprint lives
Per-project sprint tracking convention (see CLAUDE.md → Multi-Client Governance).
All sprint files live under:
clients/{{CLIENT_SLUG}}/projects/{{PROJECT_SLUG}}/sprints/
sprint-001.md
sprint-002.md
...
CURRENT -> sprint-NNN.md (symlink to the active sprint)
Sprints are per-project only. Never write sprint files to specs/,
to the client root, or anywhere shared across projects.
Step 0: Resolve the sprint directory and next number
-
Read
CLIENT_SLUGandPROJECT_SLUGfrom the active client lock (.claude/sessions/<SESSION_ID>.client). If none, stop and tell the user to run/use-client <slug> <project>first. -
Set
SPRINTS_DIR=clients/<CLIENT_SLUG>/projects/<PROJECT_SLUG>/sprints. Create it if missing:mkdir -p "$SPRINTS_DIR" -
Auto-detect the next sprint number by scanning existing files:
last=$(ls "$SPRINTS_DIR"/sprint-*.md 2>/dev/null \ | sed -E 's/.*sprint-0*([0-9]+)\.md/\1/' \ | sort -n | tail -1) next=$(( ${last:-0} + 1 )) printf -v NUMBER 'sprint-%03d' "$next"So the new file path is
$SPRINTS_DIR/$NUMBER.md(e.g.sprint-007.md). -
Refuse to overwrite an existing file. If
$SPRINTS_DIR/$NUMBER.mdexists, stop and ask the user how to proceed.
Step 1: Account Lead — Client Commitments
Define:
- Client commitments this sprint
- Non-negotiables and hard deadlines
Step 2: Product Manager — Sprint Goal & Backlog Selection
PM owns prioritization:
- Sprint goal (one sentence: what will be true when sprint ends?)
- Review open items in
clients/{{CLIENT_SLUG}}/projects/{{PROJECT_SLUG}}/specs/, prior sprints in$SPRINTS_DIR/, and the GitHub issue tracker - Select sprint backlog based on: priority, dependencies, team capacity, sprint goal alignment
- Write user stories for each selected item if not already written
- Group backlog into milestones — coherent deliverables the team commits to inside this sprint
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 · 108 lines · 22 tokens per session scan A 0220a419752e
sprint-plan is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 985 once invoked, about $0.0001 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.