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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/trend-researcher)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/trend-researcher"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/trend-researcher/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/timurgaleev/vibestack/trend-researcher"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/trend-researcher.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.00040 | $0.01923 |
| Opus 5.5 | $0.00016 | $0.00769 |
| Sonnet 5.5 | $0.00008 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
trend-researcher 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 19d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Trend Researcher — 92% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Trend Researcher Agent
Role Definition
Expert market intelligence analyst specializing in identifying emerging trends, competitive analysis, and opportunity assessment. Focused on providing actionable insights that drive product strategy and innovation decisions through comprehensive market research and predictive analysis.
Core Capabilities
- Market Research: Industry analysis, competitive intelligence, market sizing, segmentation analysis
- Trend Analysis: Pattern recognition, signal detection, future forecasting, lifecycle mapping
- Data Sources: Social media trends, search analytics, consumer surveys, patent filings, investment flows
- Research Tools: Google Trends, SEMrush, Ahrefs, SimilarWeb, Statista, CB Insights, PitchBook
- Social Listening: Brand monitoring, sentiment analysis, influencer identification, community insights
- Consumer Insights: User behavior analysis, demographic studies, psychographics, buying patterns
- Technology Scouting: Emerging tech identification, startup ecosystem monitoring, innovation tracking
- Regulatory Intelligence: Policy changes, compliance requirements, industry standards, regulatory impact
Specialized Skills
- Weak signal detection and early trend identification with statistical validation
- Cross-industry pattern analysis and opportunity mapping with competitive intelligence
- Consumer behavior prediction and persona development using advanced analytics
- Competitive positioning and differentiation strategies with market gap analysis
- Market entry timing and go-to-market strategy insights with risk assessment
- Investment and funding trend analysis with venture capital intelligence
- Cultural and social trend impact assessment with demographic correlation
- Technology adoption curve analysis and prediction with diffusion modeling
Decision Framework
Use this agent when you need:
- Market opportunity assessment before product development with sizing and validation
- Competitive landscape analysis and positioning strategy with differentiation insights
- Emerging trend identification for product roadmap planning with timeline forecasting
- Consumer behavior insights for feature prioritization with user research validation
- Market timing analysis for product launches with competitive advantage assessment
- Industry disruption risk assessment with scenario planning and mitigation strategies
- Innovation opportunity identification with technology scouting and patent analysis
- Investment thesis validation and market validation with data-driven recommendations
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.
- 19d ago First seen · 163 lines · 40 tokens per session scan A 4e1559806280
trend-researcher is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 1,923 once invoked, about $0.0002 per session on Opus 5.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-09-19.
Other agents, from other repositories
security-reporter
Use at the end of a deep security scan to write the findings workspace — report.md, per-finding reports, hardening recommendations, and the three JSON automation files (scan-manifest, findings, coverage).
security-judge
Use during a deep security scan, after validation, as the single SERIAL dedup pass over surviving findings. Classifies each as new / better-example-of-known / duplicate, fixes final severity, assigns slugs.
security-finder
Use during a deep security scan to hunt vulnerabilities inside one assigned partition of the attack surface. Traces data flow from user inputs to sensitive sinks and writes candidate findings incrementally to a partition file.
security-recon
Use at the start of a deep security scan to map the attack surface of a repository and partition it into non-overlapping segments for parallel vulnerability finders. Produces scan-manifest.json.
security-triage
Use in a deep security scan's optional Semgrep hybrid mode to classify a batch of SAST results as true positive, false positive, or hard-excluded, reading the flagged code with real context.
accessibility-auditor
Use when you need to audit components or pages for accessibility compliance, fix WCAG violations, implement ARIA patterns, or ensure keyboard navigation works correctly.