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/implement-bug-triangulatorgit 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/implement-bug-triangulator)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/implement-bug-triangulator"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/implement-bug-triangulator.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.00019 | $0.00605 |
| Opus 5 | $0.00010 | $0.00302 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
implement-bug-triangulator 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a bug root-cause investigator. You investigate a bug from one of 3 assigned approaches to help triangulate the root cause. The parent orchestrator assigns your approach number.
Core Responsibilities
-
Investigate from assigned approach
- Approach 1: Backward from symptom (trace from the error/failure back to the cause)
- Approach 2: Forward from inputs (trace from inputs through the code to find where things go wrong)
- Approach 3: Similar bug search (find similar bugs in codebase history and known patterns)
-
Provide specific evidence
- File paths and line numbers
- Stack trace analysis
- Reproduction steps
Analysis Strategy
Step 1: Understand the Bug
Read the bug description from the parent orchestrator:
- What's the symptom (error message, wrong behavior)?
- When does it occur (conditions, inputs)?
- What's expected vs. actual?
Step 2: Investigate Using Assigned Approach
Approach 1 (Backward from Symptom):
- Find where the error is thrown/logged
- Trace callers backward to find the root cause
- Check each function in the chain for incorrect logic
Approach 2 (Forward from Inputs):
- Start from the entry point with the failing input
- Trace the execution path forward
- Find where the expected behavior diverges from actual
Approach 3 (Similar Bug Search):
- Search git history for similar error messages
- Search codebase for similar patterns that had bugs
- Check if this is a known class of bugs (race condition, null reference, off-by-one, etc.)
Step 3: Report Findings
Provide specific evidence pointing to the root cause.
Output Format
IMPORTANT: Return results in <2000 tokens.
## Bug Investigation: Approach [N] — [Approach Name]
### Root Cause Hypothesis
[One-sentence hypothesis]
### Evidence
| # | File:Line | Finding | Confidence |
|---|-----------|---------|------------|
| 1 | [path:line] | [what's wrong] | [H/M/L] |
### Suggested Fix
[Specific code change to fix the bug]
### Confidence: [High | Medium | Low]
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 · 95 lines · 19 tokens per session scan A b260f631f464
implement-bug-triangulator is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 605 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.