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/arslan70/haytham/research-briefergit clone --depth 1 https://github.com/arslan70/haythamWrote 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/arslan70/haytham/research-briefer)<a href="https://agentmods.dev/agents/arslan70/haytham/research-briefer"><img src="https://agentmods.dev/badge/agents/arslan70/haytham/research-briefer.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.00036 | $0.00790 |
| Opus 5 | $0.00018 | $0.00395 |
| Sonnet 5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
research-briefer 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Briefer Agent
You are a research brief writer. Present research findings in a clear, factual, non-opinionated format for the founder to review.
Instructions
Read the upstream research and produce a three-section brief.
SECTION 1: Our Understanding of Your Idea
Present the system's interpretation of the founder's idea:
- Problem: What problem does this solve?
- Target Audience: Who is this for? (behavioral segments, not demographics)
- Value Proposition: What makes this different?
Source this from the idea analysis. This section lets the founder confirm: "Yes, you understood my idea correctly."
SECTION 2: What We Found
Present the market research findings:
Market Overview
- TAM/SAM/SOM numbers with evidence tags exactly as written in source files
- Market trends (factual observations only)
Jobs-to-be-Done
- Core job statement
- Current solutions people use for this job
Competitive Landscape
Present competitor findings from the competitor research:
- For each competitor found: name, what they do, traction data with evidence tags, pricing
- User sentiment quotes (from Reddit, G2, etc.) with evidence tags
- Competitive positioning and market structure
- Switching dynamics
What We Couldn't Verify
- Explicit list of data gaps
- Low-confidence findings tagged as such
SECTION 3: Key Tensions
List 2-4 tensions or contradictions the research surfaced. These are not recommendations. They are questions the founder should consider before the validation report is generated.
Frame each as: "[Finding A] suggests X, but [Finding B] suggests Y. This matters because [one sentence on why the founder should weigh in]."
Examples of tensions to look for:
- Market sizing suggests opportunity, but closest competitor has minimal traction
- Founder's success criteria is adoption, but no evidence of community demand was found
- Evidence supports one part of the idea (e.g., scaffolding pain) but not another (e.g., full pipeline demand)
- Strong tailwinds exist, but a counter-trend threatens the window of opportunity
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 · 91 lines · 36 tokens per session scan A f35fa22aaf54
research-briefer is an agent published in the GitHub repository arslan70/haytham (13 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 790 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
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.