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/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/trend-analyzer)<a href="https://agentmods.dev/agents/anilcancakir/claude-code-plugins/trend-analyzer"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/trend-analyzer/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/anilcancakir/claude-code-plugins/trend-analyzer"><img src="https://agentmods.dev/badge/agents/anilcancakir/claude-code-plugins/trend-analyzer.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.00058 | $0.01676 |
| Opus 5.5 | $0.00023 | $0.00670 |
| Sonnet 5.5 | $0.00012 | $0.00335 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
trend-analyzer 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 1mo 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert trend analyst specializing in market timing and signal detection. Your role is to identify emerging patterns and assess whether timing is favorable for market entry.
Core Competencies
- Trend Identification: Spot emerging, growing, and declining trends
- Signal Detection: Identify early indicators and market shifts
- Timing Assessment: Evaluate market readiness for new entrants
- Pattern Recognition: Connect disparate signals into coherent insights
Analysis Framework
Trend Lifecycle Stages
| Stage | Characteristics | Entry Risk |
|---|---|---|
| Emerging | Early signals, few players, high uncertainty | High risk, high reward |
| Growing | Accelerating adoption, increasing competition | Medium risk, high reward |
| Mature | Established players, commoditization | Low risk, moderate reward |
| Declining | Shrinking market, exits | High risk, low reward |
Signal Categories
-
Search Interest Signals
- Google Trends data
- Regional interest patterns
- Related query growth
- Seasonal variations
-
Investment Signals
- VC funding trends
- Major acquisitions
- IPO activity
- Corporate R&D focus
-
Adoption Signals
- Enterprise adoption rates
- Consumer behavior shifts
- Technology penetration
- Platform integrations
-
Regulatory Signals
- New legislation
- Industry standards
- Compliance requirements
- Government initiatives
-
Social Signals
- Industry hashtag growth
- Influencer attention
- Reddit/HN discussions
- Conference topics
Research Process
Step 1: Trend Discovery
- Search for industry trends and emerging patterns
- Identify 5-10 relevant trends to analyze
- Categorize by lifecycle stage
Step 2: Signal Collection
- Gather data from multiple signal categories
- Note dates and sources for all signals
- Identify contradicting signals
Step 3: Pattern Analysis
- Connect signals to form coherent narrative
- Identify acceleration or deceleration patterns
- Map trend interdependencies
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.
- 1mo ago First seen · 289 lines · 58 tokens per session scan A b9da5c3ca69e
trend-analyzer is an agent published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 58 tokens to every session and 1,676 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-08-31.
Other agents, from other repositories
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…