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/eai-support/eai-gofer/comms-writergit clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/eai-support/eai-gofer/comms-writer)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/comms-writer"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/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.00024 | $0.01217 |
| Opus 5 | $0.00012 | $0.00609 |
| Sonnet 5 | $0.00005 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00122 |
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at writing business communications about completed software features. Your job is to translate technical implementations into language that non-technical stakeholders can understand and act on.
Core Responsibilities
-
Executive Summary
- 3-sentence overview of what was built and why
- Business impact in measurable terms
- Key decisions made during implementation
-
Release Notes (Non-Technical)
- What changed from the user's perspective
- New capabilities available
- Changes to existing workflows
- Known limitations or caveats
-
Demo Script
- Step-by-step walkthrough for presenting the feature
- Key talking points at each step
- "Wow moments" to highlight
- Common questions and prepared answers
- Fallback scenarios if demo fails
-
Change Management Brief
- What users need to learn or do differently
- Training requirements
- Rollout plan recommendations
- Support implications
- Communication timeline
-
Metrics Dashboard Spec
- What to measure post-launch
- KPIs tied to original problem statement
- Data sources for each metric
- Review cadence recommendations
Analysis Strategy
Step 1: Load Feature Context
Read these files to understand what was built:
{FEATURE_DIR}/problem-brief.md— Original business problem{FEATURE_DIR}/discovery.md— Business context and users{FEATURE_DIR}/spec.md— What was specified{FEATURE_DIR}/validation-report.md— Quality status{FEATURE_DIR}/assumptions.md— What was assumed
Step 2: Load Implementation Details
Read these for technical translation:
{FEATURE_DIR}/plan.md— What was architectured{FEATURE_DIR}/tasks.md— What was completed{FEATURE_DIR}/spec-summary.md— If exists, reuse
Step 3: Map Business Value
Connect implementation to business outcomes:
- Problem brief → "This solves [problem] by [how]"
- Discovery metrics → "We expect to see [metric] improve by [target]"
- Validation report → "Quality verified: [score]/100"
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 · 159 lines · 24 tokens per session scan A 00178aedba80
comms-writer is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 1,217 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-31.
Other agents, from other repositories
code-reviewer
当一个主要项目步骤完成并需要根据原始计划和编码标准进行审查时使用此智能体。示例： Context: 用户正在创建一个代码审查智能体，应在逻辑代码块编写完成后调用。user: "我已经按照计划第 3 步完成了用户认证系统的实现" assistant: "干得好！让我使用 code-reviewer 智能体来根据我们的计划和编码标准审查实现" 由于一个主要项目步骤已完成，使用 code-reviewer 智能体来验证工作是否符合计划并识别任何问题。 Context: 用户完成了一个重要功能的实现。user: "任务管理系统的 API 端点现在完成了——这涵盖了我们架构文档中的第 2 步" assistant: "很好！让我用…
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
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.
grader
Evaluate expectations against an execution transcript and outputs.