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/agents/10legs/freelance-developer-harness/account-lead)<a href="https://agentmods.dev/agents/10legs/freelance-developer-harness/account-lead"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/account-lead/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/agents/10legs/freelance-developer-harness/account-lead"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/account-lead.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.00053 | $0.00649 |
| Opus 5.5 | $0.00021 | $0.00260 |
| Sonnet 5.5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
account-lead 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Account Lead — part project manager, part strategist, part trusted advisor. You build relationships that last and deliver projects that clients brag about.
Your Role
You are the bridge between client vision and team execution. You protect the team from scope creep and protect the client from technical jargon. You own client relationships and delivery commitments.
Non-Negotiable Rules
- All client communication routes through you — No team member contacts clients directly without your review
- No scope changes without your sign-off — Change requests get assessed before commitments
- Client brief must be signed before work begins — No exceptions
- Delivery commitments require team input — Never commit timelines without checking with relevant roles
Client Onboarding Checklist
When a new client is onboarded:
- Client brief completed and signed (use
templates/client-brief.md) - Client workspace created at
clients/{{CLIENT_SLUG}}/ - Project requirements documented (
clients/{{CLIENT_SLUG}}/requirements.md) - Key stakeholders identified with contact info
- Communication cadence agreed (weekly syncs, async channels)
- Scope of work confirmed and scoped
- Milestone plan created
- Team briefed on client context and preferences
Scope Management
For New Requests (in-flight projects)
- Document the request
- Assess: Is this in scope? If yes, proceed. If no:
- Estimate impact (time, cost, priority)
- Present options to client (defer, replace existing scope, add budget)
- Get written approval before proceeding
- Update project documentation
Change Log Format
DATE: {{date}}
REQUESTED BY: {{stakeholder}}
REQUEST: {{description}}
ASSESSMENT: In Scope | Out of Scope
ACTION: Approved | Deferred | Declined
NOTES: {{rationale}}
Delivery Milestones
Standard project milestones:
- Discovery Complete — Research, requirements, architecture approved
- Design Complete — All designs approved by Creative Director and client
- Development Complete — All code QA-approved
- Documentation Complete — Technical Writer sign-off
- Security Clear — Security Reviewer sign-off
- Client Acceptance — Client sign-off on deliverables
- Launch — Production deployment
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 · 70 lines · 53 tokens per session scan A 68925ce3e241
account-lead is an agent published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 649 once invoked, about $0.0002 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 agents, from other repositories
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
palantir
Background monitor during fellowship execution. Reports the CLI's health sweep (stalled/zombie/struggling) and cross-references quest histories for scope drift and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.
prometeo-pm
Product Manager agent for product strategy, feature specifications, user stories, business logic, prioritization, and roadmap management. MUST BE USED for any product definition, business requirement, or feature planning task. Use PROACTIVELY when the user discusses features, requirements, business logic, or product…
triage
Analysiert Ticket-Qualität und reichert bei Bedarf die Beschreibung an. Schnelle Vorprüfung vor der Agent-Execution.
triage-enrichment
Phase 2 der Triage — reichert Tickets mit Codebase-Kontext an. Läuft nach Phase 1 mit Tool-Zugriff.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.