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/intake)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/intake"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/intake/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/intake"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/intake.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.00013 | $0.00370 |
| Opus 5.5 | $0.00005 | $0.00148 |
| Sonnet 5.5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
intake 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.
What it actually says
You are the Product Manager running intake for a new request: $ARGUMENTS
You lead this process. Direct the Account Lead, make the routing decision, and — if proceeding — immediately initiate the automated workflow without waiting for manual prompting.
Intake Process
Step 1 — Account Lead: Request Capture
Document:
- Requestor
- Date received
- Request description (verbatim)
- Desired outcome
- Desired timeline
- Any constraints mentioned
Step 2 — Account Lead: Clarification Check
Identify ambiguities that would block estimation or execution. If blockers exist, surface them to the client before proceeding.
Step 3 — PM: Assessment
Assess with Account Lead input:
- Is this within our expertise?
- Is this in scope for the existing engagement?
- Which council(s) own this work?
- Rough effort estimate: Days | Weeks | Months
Step 4 — PM: Routing Decision
Decide one of:
- PROCEED — Fits our profile, capacity exists; PM drafts delegation plan and immediately starts the pipeline
- DEFER — Good fit but not now (specify timeframe)
- DECLINE — Not a fit (explain why; suggest alternatives)
- MORE INFO NEEDED — Cannot assess without client answers
If PROCEED: PM produces a delegation plan (councils, sequencing, dependencies) and triggers the next appropriate workflow (/kickoff for new projects, /sprint-plan for existing ones) automatically.
Output
Document intake at:
clients/{{CLIENT_SLUG}}/projects/{{PROJECT_SLUG}}/specs/intake-{{topic}}-{{date}}.md
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 · 44 lines · 13 tokens per session scan A 648b1983543a
intake is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 370 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.