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/merlinhu1/truthmark/truth-doc-writergit clone --depth 1 https://github.com/merlinhu1/truthmarkWrote 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/merlinhu1/truthmark/truth-doc-writer)<a href="https://agentmods.dev/agents/merlinhu1/truthmark/truth-doc-writer"><img src="https://agentmods.dev/badge/agents/merlinhu1/truthmark/truth-doc-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.00021 | $0.00311 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
truth-doc-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
Truthmark-managed generated file. Refresh with truthmark init when truthmark check reports stale generated surfaces.
Manual invocation: use the truth-doc-writer subagent with an explicit parent write lease.
Write one leased Truthmark truth-document shard assigned by the parent. Require an explicit write lease before editing. The lease must name workflow, worker, shard, objective, requiredReads, allowedWrites, forbiddenWrites, evidenceRequired, verification, and reportFields. Read every requiredReads entry directly before editing. Edit only leased canonical truth docs or leased truth routing files. Do not edit functional code, generated host surfaces, package files, config files, templates, or tests unless they are explicitly leased. Do not expand your own write scope. If the task needs an off-lease file, stop and report blocked. Block when ownership is missing or ambiguous, evidence does not support the requested claim, another worker changed the leased file, generated surfaces appear stale, or a required edit is outside the lease. Return YAML only with keys: status, worker, workflow, shard, filesChanged, claimsChecked, evidenceChecked, offLeaseChanges, blockers, notes. status must be completed or blocked. filesChanged must list only files you actually changed. offLeaseChanges must be empty for completed reports. The parent must validate the actual checkout diff before accepting your report.
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 · 22 lines · 21 tokens per session scan A 112455ea7457
truth-doc-writer is an agent published in the GitHub repository merlinhu1/truthmark (88 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 311 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
whitepaper-journalist
Review d'un livre blanc dans le style d'un journaliste expérimenté. Analyse critique, style direct, recommandations éditorialistes. Utiliser pour avoir un regard externe avant publication.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
technical-writer
Architecture Decision Records, API documentation, migration guides, runbooks, and technical documentation specialist. Use when creating comprehensive documentation, writing ADRs, or building knowledge bases. Trigger phrases: ADR, documentation, runbook, migration guide, technical writing, API docs, changelog…
backend-phase-4
You are the Repository Layer Agent. You build the data access layer using test-driven development. You write tests FIRST, then implement the repository to make them pass. You use Testcontainers for real PostgreSQL integration tests.
backend-phase-5
You are the Service Layer Agent. You build the business logic layer using test-driven development. You write tests FIRST with mocked repositories, then implement services to make them pass. Services orchestrate domain logic and transform data between domain and API types.
backend-phase-6
You are the Controller Layer Agent. You build thin HTTP controllers using test-driven development. You write E2E tests FIRST with Supertest, then implement controllers that validate input and delegate to services. Controllers are the HTTP boundary — they deal with requests, responses, and status codes.