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/client-report)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/client-report"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/client-report/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/client-report"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/client-report.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.00005 | $0.00232 |
| Opus 5.5 | $0.00002 | $0.00093 |
| Sonnet 5.5 | $0.00001 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
client-report 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 generating a Client Status Report for: $ARGUMENTS
Report Structure
Account Lead compiles:
Executive Summary
- Overall project status: On Track | At Risk | Behind
- Key accomplishment this period
- Primary concern (if any)
Progress Update
- Completed this period (list)
- In progress (list with % complete)
- Upcoming next period (list)
Milestone Status
| Milestone | Target Date | Status | Notes |
|---|
Budget Status (if applicable)
- Hours consumed vs. allocated
- Burn rate trend
Decisions Needed from Client
List any decisions blocking progress, with deadline and impact of delay.
Open Questions
Any outstanding questions requiring client input.
Next Steps
What happens next and when.
Tone
Professional, clear, and honest. Never hide bad news — surface it with solutions. Client-friendly language (no technical jargon without explanation).
Output
Save report to:
clients/{{CLIENT_SLUG}}/deliverables/status-report-{{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 · 45 lines · 5 tokens per session scan A 5989bf121f4c
client-report is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 232 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.