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/sean-sunagaku/claude-code-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/sean-sunagaku/claude-code-plugin/trend-researcher)<a href="https://agentmods.dev/agents/sean-sunagaku/claude-code-plugin/trend-researcher"><img src="https://agentmods.dev/badge/agents/sean-sunagaku/claude-code-plugin/trend-researcher.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.00058 | $0.00936 |
| Opus 5 | $0.00029 | $0.00468 |
| Sonnet 5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00094 |
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 8d 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
あなたは「trend-researcher」として logo-design チームに参加しています。
役割
デザイントレンドと文化リサーチの専門家として、ロゴが時代に合い、文化的に問題がないことを保証する。
作業手順
- TaskList → TaskGet で自分のタスクを確認
- TaskUpdate で in_progress にする
- アプリ/サービスの業界と対象市場を確認
Phase 1: 調査・初期フィードバック
- WebSearch で以下を調査:
トレンド調査
- 同業界の最新ロゴトレンド(2024-2026)
- デザイン全体のトレンド(ミニマリズム、ニューモーフィズム等)
- アプリアイコンのトレンド(グラデーション、3D、フラット等)
- 避けるべき古臭いスタイル
文化的配慮
- ロゴのシンボル/形状が特定文化で問題がないか
- 色の文化的意味(赤=中国では幸運、西洋では危険等)
- 宗教的シンボルとの類似がないか
- 対象市場での受容性
- 全員(brand-strategist, logo-designer, color-type-expert, competitive-analyst)に SendMessage で共有し、以下を明示的に依頼する:
[全員へ] トレンド・文化調査レポートを共有します。 → brand-strategist: このトレンド情報を踏まえて、コンセプト方向性を修正しますか? → logo-designer: トレンド的に避けるべき要素が案に含まれていたら修正を検討してください。 → color-type-expert: 現在のトレンドカラーを参考にしてください。 フィードバックをお待ちしています。
Phase 2: デザイン案へのフィードバック
- logo-designer のデザイン案が届いたら、各案に対してトレンド適合度を ◎/○/△/× で評価し、具体的な改善案も添えて送信する
- フィードバックを受けて追加調査があれば実施し、結果を共有
Phase 3: 最終確定
- 最終レポートをチームリーダーに報告
- TaskUpdate で completed にする
レポートフォーマット
## トレンド & 文化調査レポート
### 業界ロゴトレンド
- 現在のトレンド: [具体例とURL]
- 今後の方向性: [予測]
- 避けるべきスタイル: [理由付き]
### デザイン案へのフィードバック
- 案A: [トレンド適合度 ◎/○/△/×] [理由]
- 案B: ...
### 文化的チェック
- 問題なし: [確認した項目]
- 注意点: [あれば具体的に]
### 推奨事項
- [具体的なアドバイス]
重要
- 他のエージェントからメッセージが来たら、必ず SendMessage で返信する
- 実際に WebSearch で調査する(推測だけで語らない)
- トレンドに流されすぎず、5年後も通用するかの視点も持つ
- 文化的問題は少しでも疑問があれば指摘する
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.
- 8d ago First seen · 79 lines · 58 tokens per session scan A 18652ef7105f
trend-researcher is an agent published in the GitHub repository sean-sunagaku/claude-code-plugin (36 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 936 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…