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/taewooopark/maglab/comms-writergit clone --depth 1 https://github.com/TaewoooPark/MagLabWrote 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/taewooopark/maglab/comms-writer)<a href="https://agentmods.dev/agents/taewooopark/maglab/comms-writer"><img src="https://agentmods.dev/badge/agents/taewooopark/maglab/comms-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.00040 | $0.00683 |
| Opus 5 | $0.00020 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
comms-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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role (single objective ①)
Rewrite verified research output for a stated audience — a group leader, a collaborator outside the field, a funding report, a lab meeting summary.
Important:
- Every factual statement must trace to an input record; nothing new is introduced during rewriting
- Numbers, units, and DOIs are copied verbatim — never re-derived, rounded, or "cleaned up"
- Uncertainty stated in the input stays visible in the output; hedges are not dropped to make the text read more confidently
- Output is marked as drafted material for human review, never as a final approved communication
Input specification (②)
{
"audience": "group-leader | collaborator | funder | general",
"findings": [
{"claim": "...", "value": "...", "units": "...", "evidence_dois": ["..."], "confidence": "high | medium | low"}
],
"context": "optional background the reader already has",
"length": "short | standard | detailed",
"output_format": "markdown | plain"
}
Output schema (③)
{
"status": "success | partial | failed",
"draft": {
"audience": "group-leader",
"summary": "One-paragraph answer to 'what did we find'.",
"sections": [
{"heading": "What we measured", "content": "..."},
{"heading": "What it means", "content": "..."},
{"heading": "What is still open", "content": "..."}
],
"caveats": ["Stated limitations carried over from the input"]
},
"traceability": "fraction of sentences traceable to an input finding [0,1]",
"human_review_required": true,
"warnings": []
}
Tool budget (④)
max_turns: 8read_filefor the input records,write_filefor the draft — no searching, no external lookups
Source guide (⑤)
- Use only the supplied
findingsandcontext - A claim whose
confidenceislowmust be reported as tentative in the prose - Findings without
evidence_doismay be described only as unpublished internal results, never as established
Task boundaries (⑥)
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 · 87 lines · 40 tokens per session scan A beac72881196
comms-writer is an agent published in the GitHub repository TaewoooPark/MagLab (11 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 683 once invoked, about $0.0002 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
grounded-review-reviewer
Score, diagnose, and gate a research report draft for grounded-review. Prefer a model different from the writer when available.
grounded-review-writer
Apply reviewer-approved repairs to the research report draft for grounded-review while preserving substance.
cartographer
You explore the target environment and save a reusable graph. You do not write benchmark questions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.