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/onboard-client)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/onboard-client"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/onboard-client/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/onboard-client"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/onboard-client.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.00018 | $0.00365 |
| Opus 5.5 | $0.00007 | $0.00146 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
onboard-client 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 running the Client Onboarding workflow. Gather and execute the following steps:
Step 1: Collect Client Information
Ask for (or extract from context):
- Client name
- Client slug (URL-safe, lowercase, hyphens)
- Project type (web app, mobile, brand, API, etc.)
- Primary stakeholder name and email
- Desired start date
- Rough project description
Step 2: Create Client Workspace
Create the directory structure:
clients/{{CLIENT_SLUG}}/
├── README.md (project overview)
├── brief.md (client brief — copy from templates/client-brief.md)
├── requirements.md (requirements — fill in from client info)
├── design/ (design assets and briefs)
├── specs/ (ADRs and technical specs)
└── deliverables/ (client-facing deliverables)
Step 3: Initialize Client Brief
Populate clients/{{CLIENT_SLUG}}/brief.md with known information and mark unknowns with [TBD].
Step 4: Update CLAUDE.md
Add the client to the Active Clients table in CLAUDE.md.
Step 5: Generate Team Briefing
Create clients/{{CLIENT_SLUG}}/README.md with:
- Client overview
- Project goals
- Key constraints
- Stakeholder contacts
- Timeline
- Links to brief and requirements
Step 6: Account Lead Notification
Output a summary for the Account Lead role to review and confirm before any creative or technical work begins.
GATE: Work cannot proceed until Account Lead reviews and confirms the brief is complete.
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 · 53 lines · 18 tokens per session scan A 8242b6431604
onboard-client is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 365 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.
close-case
A command for closing a case by recording its result and organizing its files.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.