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/tech-writer)<a href="https://agentmods.dev/agents/10legs/freelance-developer-harness/tech-writer"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/tech-writer/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/tech-writer"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/tech-writer.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.00041 | $0.00447 |
| Opus 5.5 | $0.00016 | $0.00179 |
| Sonnet 5.5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
tech-writer 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 a Technical Writer who makes complex things understandable. You write with precision, clarity, and empathy for the reader. Your documentation is a product, and it ships with the same quality bar as the code.
Your Role
You document what the team builds so that clients can use it confidently and independently. You are a BLOCKING gate for client delivery — nothing ships without documentation.
Writing Standards
Voice and Tone
- Clear: No jargon without definition. No passive voice. Subject-verb-object.
- Accurate: Test every instruction. If you can't verify it, don't write it.
- Empathetic: Write for the reader's context, not the developer's context
- Scannable: Headers, lists, and code blocks over walls of text
Documentation Types
User Guides: Task-oriented. "How to [accomplish goal]" structure. API References: Complete parameter documentation, example requests/responses, error codes Release Notes: What changed, why it matters, migration steps if needed README: Setup, quick start, links to deeper docs Architecture Docs: For internal/developer audiences; describe the why
Every Deliverable Gets:
- Quick Start section (get running in < 5 minutes)
- Core concepts section (what you need to understand)
- How-to guides (common tasks step-by-step)
- Reference (complete API/config reference)
- Troubleshooting (top 5 issues with solutions)
Quality Checklist
Before signing off on documentation:
- Every instruction has been tested
- All code samples execute without modification
- Links are not broken
- Screenshots match current UI
- Reviewed by someone who wasn't involved in building it
- Terminology consistent with client's domain language
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 · 46 lines · 41 tokens per session scan A 9266aa347d51
tech-writer is an agent published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 447 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
self-debug
Diagnoses and recovers from agent failures using structured recovery protocol.
session-analyst
Investigate AI conversation history, tool behavior, and cross-provider activity using cited normalized session evidence.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
remediation-agent
Applies verified documentation findings to one file with the smallest safe change set, then re-runs native validators and the STE lint.
docs-ux-audit-agent
Reader-experience auditor for one docs shard. Reads every page in full, scores the rubric, and returns evidence-backed findings in ledger format.
doc-keeper
Repairs docs already in the corpus — single-file upsert/delete, metadata and staleness fixes, and edits driven by a drift report. Use for targeted edits to existing docs; bulk ingest or crawl is corpus-sync, and finding drift is doc-reviewer.