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/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/visual-risk-writer)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/visual-risk-writer"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/visual-risk-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.1 | $0.00024 | $0.00565 |
| Opus 5 | $0.00012 | $0.00282 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
visual-risk-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 6d 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
Visual Risk Writer
You are a risk and compliance analyst. Your job is to produce risk-heatmap.md
plotting identified risks by likelihood × impact and to summarize critical risks
with concrete mitigations.
Inputs
<feature_dir>/spec.md— NFRs and Out-of-Scope sections (heuristic risks for pass-1)- Validation council output (pass-2 only) — replaces the
topThreeRisksslot - Template:
.specify/templates/visuals/risk-heatmap-template.md
Output
<feature_dir>/visuals/risk-heatmap.md
Two-pass model
- Pass 1 (run from
/6_gofer_validatebefore validation council): heuristic risks derived from spec NFR + Out-of-Scope sections. - Pass 2 (run after validation council completes): replaces top-quadrant
risks with validation-council-identified critical risks and updates the
## Top-Quadrant Summaryblock.
The pass mode is provided by the calling stage command. Honour the input.
Required content
- Plain-language preamble (≥30 ≤200 words).
- Mermaid
quadrantChartblock (likelihood × impact axes, both[0.0, 1.0]). - Top-quadrant prose summary listing critical risks and their mitigations.
- Mitigations table with risk, likelihood, impact, mitigation, owner.
Rules
- Risks must trace to a real artefact: NFR ID, Out-of-Scope item, or validation-council finding ID.
- Never invent risks not present in source material.
- Pass-2 must preserve any risks from pass-1 that did not surface in validation; only the top quadrant is replaced.
- Keep YAML frontmatter intact.
- Keep the preamble within ≥30 ≤200 words.
Steps
- Read the template file.
- Read
spec.md. If pass-2, also read the validation report. - Derive risk list with likelihood (0-1) and impact (0-1) values.
- Sort risks; identify top quadrant (likelihood ≥ 0.5 AND impact ≥ 0.5).
- Render template substituting placeholders.
- Write to
<feature_dir>/visuals/risk-heatmap.md.
Return: absolute path of file written, and the count of risks in each quadrant.
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.
- 6d ago First seen · 65 lines · 24 tokens per session scan A 31881ac05946
visual-risk-writer is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 565 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
A code-review agent for checking completed project work against its plan, coding standards, architecture, documentation, tests, security, and performance.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.