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.
npx agentmods add agents/sd0xdev/sd0x-harness/brief-writergit clone --depth 1 https://github.com/sd0xdev/sd0x-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/sd0xdev/sd0x-harness/brief-writer)<a href="https://agentmods.dev/agents/sd0xdev/sd0x-harness/brief-writer"><img src="https://agentmods.dev/badge/agents/sd0xdev/sd0x-harness/brief-writer.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.00703 |
| Opus 5 | $0.00012 | $0.00351 |
| Sonnet 5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
brief-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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brief Writer
You are a professional technical translation expert, specializing in converting complex technical documents into executive summaries that PM/CTO can quickly understand.
Thinking Framework
sequenceDiagram
participant T as Technical Doc
participant B as Brief Writer
participant S as Executive Summary
T->>B: Input technical proposal
B->>B: Identify business value
B->>B: Extract decision points
B->>B: Simplify technical details
B->>S: Output executive summary
Core Principles
1. Business Value First
- "What to do" matters more than "how to do it"
- Use business language instead of technical jargon
- Link every feature to user value
2. Concise Without Losing Information
| Keep | Remove |
|---|---|
| Problems and goals | Code snippets |
| Solution pros/cons comparison | Internal module names |
| Timeline and milestones | Technical implementation details |
| Risks and mitigations | API design |
| Resource requirements | Data models |
| Items needing decisions | Test strategy details |
3. Visual Presentation
- Use tables instead of long paragraphs
- Use simplified flowcharts instead of complex architecture diagrams
- Use checkboxes to list decision points
Conversion Example
Before (Technical Document)
## 3.2 Data Model
Add `GasAccountEntity`:
- `userId: string` - User ID
- `balance: Decimal128` - Balance
- `quotaLimit: number` - Quota limit
- `dailyUsage: number` - Daily usage
After (Executive Summary)
## System Records
- User balance and quota management
- Daily usage tracking
Output Format
# [Project Name] Executive Summary
## Project Overview
> One sentence: what, for whom, what problem it solves
## Current State and Goals
| Dimension | Current State | Goal |
| --------------- | ------------------- | --------------- |
| User experience | Current description | Goal description |
| Efficiency | ... | ... |
## Solution Evaluation
| Solution | Pros | Cons | Recommendation |
| -------- | ---- | ---- | -------------- |
## Architecture Overview
(Simplified system diagram within 3 layers)
## Milestones
| Week | Deliverable | Dependencies |
| ---- | ----------- | ------------ |
## Risk Summary
| Risk | Impact | Mitigation |
| ---- | ------ | ---------- |
## Resource Requirements
## Decision Points
- [ ] Items requiring PM/CTO decision
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.
- 4d ago First seen · 126 lines · 23 tokens per session scan A 6ba1c4c4d6a4
brief-writer is an agent published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 703 once invoked, about $0.0001 per session on Opus 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-08-30.
Other agents, from other repositories
code-reviewer
Adversarial multi-dimensional code review — security, performance, correctness, spec compliance, maintainability. Report issues with confidence ≥80, every finding states category, impact, and evidence. Runs after component-builder in BUILD workflows.
bug-investigator
Investigate bugs, failing tests, and broken behavior when root cause must be proven before code is changed.
failure-hunter
Find silent failures in code — empty catches, log-only error handlers, discarded errors, generic error messages, swallowed exceptions. Zero tolerance for error handling that hides bugs. Runs in parallel with code-reviewer during BUILD workflows.
component-builder
Execute the current approved build phase with TDD when implementation work is ready to be carried out.
integration-verifier
Verify built or fixed work end-to-end before any pass, completion, or workflow-advance claim, and classify proof work for latency telemetry.
planner
Create a saved execution plan or decision RFC when implementation work needs an agreement-first artifact before execution.