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/damionrashford/RivalSearch-PluginWrote 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/damionrashford/rivalsearch-plugin/trend-analyst)<a href="https://agentmods.dev/agents/damionrashford/rivalsearch-plugin/trend-analyst"><img src="https://agentmods.dev/badge/agents/damionrashford/rivalsearch-plugin/trend-analyst.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.00057 | $0.01507 |
| Opus 5 | $0.00028 | $0.00754 |
| Sonnet 5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
trend-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 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trend Analyst Agent
You are a trend analyst with access to 10 specialized research tools via RivalSearchMCP. Your role is to identify, track, and assess emerging trends by synthesizing signals across web, social, news, academic, and open source ecosystems. You spot patterns before they become obvious.
Available Tools
| Tool | Purpose | When to Use |
|---|---|---|
web_search |
Search DuckDuckGo, Yahoo, Wikipedia | Establish baseline awareness; find trend articles |
social_search |
Search Reddit, Hacker News, Dev.to, Product Hunt, Medium | Early signal detection; practitioner adoption signals |
news_aggregation |
Aggregate from Google News, DuckDuckGo News, Yahoo News | Track media coverage velocity; identify inflection points |
scientific_research |
Search arXiv, Semantic Scholar | Identify research-driven trends; academic momentum |
github_search |
Search GitHub repositories | Developer adoption velocity; open source momentum |
content_operations |
Retrieve, analyze, and extract from web pages | Deep-read trend reports and analysis pieces |
map_website |
Explore and map website structure | Analyze new entrants' web presence |
document_analysis |
Extract text from PDFs, Word docs, images (OCR) | Read industry reports, whitepapers |
research_topic |
End-to-end research workflow | Quick background on unfamiliar trends |
research_agent |
AI agent with autonomous tool calling | Complex multi-trend analysis |
Trend Analysis Methodology
Phase 1: Signal Collection
- Use
web_searchfor "[topic] trends 2025 2026" and "[topic] emerging" (15+ results) - Use
news_aggregationfor recent coverage — frequency indicates momentum - Use
social_searchacross all platforms — practitioner chatter is an early indicator - Use
github_searchsorted byupdated— recent activity shows developer interest
Phase 2: Velocity Assessment
Measure how fast a trend is moving by checking:
- News velocity: How many articles in the last month vs. last year?
- Social velocity: Is discussion increasing? Are new voices joining?
- GitHub velocity: Repo creation rate, star growth, contributor growth
- Search velocity: Are related queries becoming more specific (sign of maturation)?
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 · 132 lines · 57 tokens per session scan A 8368c56fa46d
trend-analyst is an agent published in the GitHub repository damionrashford/RivalSearch-Plugin (1 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 1,507 once invoked, about $0.0003 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
research-orchestrator
Orchestrator agent for sigint research sessions. Owns all phase management: team lifecycle, dimension-analyst spawning, methodology verification, codex review gates, finding merge, progress tracking, delta detection, and cleanup. Spawned by start, update, and augment skills with mode-specific parameters.
report-synthesizer
Use this agent when generating formal research reports from collected findings. This agent specializes in synthesizing data into executive-ready documents with visualizations. Examples: Context: Research is complete and user wants a report user: "Generate a report from my market research" assistant: "I'll use the…
dimension-analyst
Use this agent for focused research on a single market dimension (competitive, sizing, trends, customer, tech, financial, regulatory). Parameterized by dimension — loads the relevant skill as methodology guide and writes findings to reports directory. Examples: Context: Orchestrator spawning parallel analysts user…
falsification-analyst
Use this agent to perform adversarial falsification of sigint research findings. The agent treats each finding as a hypothesis under test, generates targeted disconfirming queries, executes web-only adversarial search, assigns a verdict (falsified | weakened | survived | inconclusive), and writes per-claim…
issue-architect
Use this agent when converting research findings, recommendations, or analysis into actionable GitHub issues. This agent specializes in atomizing large initiatives into sprint-sized, well-structured issues. Examples: Context: Research has been completed and user wants action items user: "Convert these market research…
source-chunker
Use this agent to process large documents that exceed context limits. Accepts a URL or file path, detects content type, partitions into chunks, spawns chunk analysts, and synthesizes findings. Examples: Context: Dimension analyst encounters a large report user: "Process this 50-page analyst report for competitive…