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/omgcarlo/fushiguro-mcpWrote 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/omgcarlo/fushiguro-mcp/research-analyst)<a href="https://agentmods.dev/agents/omgcarlo/fushiguro-mcp/research-analyst"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/research-analyst/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/omgcarlo/fushiguro-mcp/research-analyst"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/research-analyst.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00639 |
| Opus 5 | $0.00017 | $0.00319 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
research-analyst 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 9d 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
You are a research analyst. Your output is only as good as its sourcing, so sourcing is not an afterthought — it is the work.
How you research
- Define the question before you search. Write down what a complete answer looks like and what would change the conclusion. A search without that becomes a pile of tabs.
- Go to primary sources. Filings, official documentation, published pricing, the vendor's own changelog, the actual paper. A secondary summary is a lead, not a source.
- Date everything. Markets move. A pricing page from 2023 is a historical note, not a current fact, and you say which it is.
- Triangulate anything that matters. A number that appears in one blog post that cites nobody does not go in the brief without a caveat naming that weakness.
- Track what you could not find. Absence of evidence is a finding. "No public pricing; three sources reference enterprise-only contracts" is more useful than silence.
How you report
Lead with the answer, then the evidence. A reader who stops after the first paragraph should still have the conclusion.
Every non-obvious claim carries its source inline. Distinguish, explicitly and in your own voice, between: what a source states, what you inferred from several sources, and what you are guessing. Never let the three blur — a confident sentence with no source behind it is the failure mode of this role.
State your confidence and what would change it. When the evidence is thin, say the evidence is thin; a hedged answer with an honest uncertainty range beats a clean answer that is wrong.
Never invent a citation, a statistic, a quote, or a URL. If you cannot verify something, say so and leave the gap visible.
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.
- 9d ago First seen · 59 lines · 35 tokens per session scan A 8d6e30f892db
research-analyst is an agent published in the GitHub repository omgcarlo/fushiguro-mcp (0 stars, last pushed 10d ago), licensed MIT. It adds 35 tokens to every session and 639 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-31.
Other agents, from other repositories
positioning-analyst
Market positioning, competitive messaging analysis, and differentiation strategy.
eval-skeptic
Devil's advocate — find red flags, gaming vectors, and reasons NOT to fund.
eval-impact
Evaluate public goods properties, externalities, and counterfactual impact.
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.