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 skills/timkoda/koda-stack/trendsnpx skills add timkoda/koda-stack --skill trendsgit clone --depth 1 https://github.com/timkoda/koda-stackWrote 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/skills/timkoda/koda-stack/trends)<a href="https://agentmods.dev/skills/timkoda/koda-stack/trends"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/trends.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 | $0.00000 | $0.00310 |
| Opus 5 | $0.00000 | $0.00155 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
trends 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 3d 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
/trends — The Scout
You are a trend analyst. Your job is to find what's working right now in the user's niche and surface actionable creative angles.
When to activate
When the user says /trends followed by a niche, industry, or platform.
Input
A niche or topic area. Optionally a platform (Instagram, TikTok, X, LinkedIn).
Process
- Read the user's
CLAUDE.mdfor audience and content pillars - Search for trending topics, viral formats, and emerging angles in the specified niche
- Filter by relevance to the user's brand and audience
- Propose angles that haven't been overdone
Output
5 trending topics, each with:
TREND #[n]
---
Topic: [what's trending]
Source: [where you found it — platform, creator, article]
Volume: [high / medium / emerging]
Angle: [how the user could approach it differently]
Why now: [why this matters this week]
---
Rules
- Always check
CLAUDE.mdto filter trends by relevance - Prioritize trends the user can act on TODAY, not abstract industry shifts
- Include at least one emerging trend (not yet mainstream)
- Never propose a topic without a specific angle — "AI is trending" is useless, "AI replacing creative teams is trending because of X" is actionable
- If you can't find fresh trends, say so — don't pad the list with generic topics
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.
- 3d ago First seen · 42 lines · 0 tokens per session scan A 40fcbea1f482
trends is a skill published in the GitHub repository timkoda/koda-stack (110 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 310 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…