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/kickoff)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/kickoff"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/kickoff/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/kickoff"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/kickoff.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.00014 | $0.00557 |
| Opus 5.5 | $0.00006 | $0.00223 |
| Sonnet 5.5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
kickoff 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Manager running Project Kickoff for: $ARGUMENTS
You own this workflow end-to-end. Direct each agent in sequence, collect their outputs, and produce the final kickoff summary without waiting for manual prompting between steps.
Prerequisites Check
Verify before proceeding:
- Client workspace exists at
clients/{{CLIENT_SLUG}}/projects/{{PROJECT_SLUG}}/ - Client brief is complete (no
[TBD]in critical fields) - Account Lead has confirmed readiness
If any prerequisite fails, stop and surface the blocker. Do not proceed.
Kickoff Sequence
Step 1 — Account Lead: Context Brief
Review clients/{{CLIENT_SLUG}}/brief.md and clients/{{CLIENT_SLUG}}/requirements.md.
Deliver to the PM: goals, constraints, success criteria, and known risks.
Step 2 — PM: Vision & Delegation Plan
Using the Account Lead's context:
- Define the product vision in one sentence
- Identify the top 3 outcomes that define success
- Break work into epics (major capability areas)
- Assign each epic to the correct council with sequencing and dependencies
- Identify the critical path
This delegation plan drives the rest of kickoff and all subsequent sprints.
Step 3 — Creative Council (PM-directed, run in parallel where possible)
Innovation Lead: Problem reframe
- What is the real problem being solved?
- What assumptions should be challenged?
- What would a breakthrough solution look like?
UX Researcher: Research plan
- Research questions to answer before design begins
- Proposed methods and participant criteria
Creative Director: Creative brief
- Brand personality or alignment
- Visual direction options
- Creative principles for this project
Step 4 — Technical Council (PM-directed)
Solution Architect: Technical feasibility assessment
- Key technical challenges
- Preliminary architecture options and recommendations
- Risks and unknowns
- Dependencies on Creative Council outputs
Step 5 — PM: Synthesis & Next Steps
Consolidate all outputs. Identify:
- Open questions that must be resolved before work begins
- Cross-council dependencies and their resolution order
- First sprint candidates
- Any gate blockers
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 · 78 lines · 14 tokens per session scan A b4d214caa126
kickoff is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 557 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.