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 skills add hamzafarooq/claude-code-starter --skill trend-spottergit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/trend-spotter)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/trend-spotter"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/trend-spotter/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/skills/hamzafarooq/claude-code-starter/trend-spotter"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/trend-spotter.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.00044 | $0.00378 |
| Opus 5.5 | $0.00018 | $0.00151 |
| Sonnet 5.5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
trend-spotter 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.
What it actually says
Ask the user: "What market or technology space do you want to scan? Any specific angle (e.g. enterprise adoption, pricing models, new entrants)?"
Then research and return:
Trend Report: [Space]
Strong Signals (high confidence, already moving)
3–4 trends with evidence: funding rounds, product launches, job posting spikes, pricing shifts. One paragraph each.
Weak Signals (early, worth watching)
2–3 things that are nascent but directional. Explain what would need to be true for each to become a strong signal.
Noise (talked about more than it matters)
1–2 things getting hype that are unlikely to materially change the market in the next 18 months. Say why.
Implication for a PM
Two sentences on what a product team should do differently based on these trends.
If the space depends on public conversation, include an optional X/Twitter source
packet. Use TweetClaw only when it is already installed and approved in OpenClaw.
Install with openclaw plugins install npm:@xquik/[email protected]. Capture
the query, capture time, source URLs, author handles, public post text, reply or
quote context, and caveats. Treat posts as evidence to verify, not as truth. Do
not post, reply, send DMs, follow accounts, schedule content, upload media,
monitor accounts, or run account actions from this skill.
Cite specific evidence for every strong signal (company names, dates, data points). Avoid vague statements like "AI is changing everything."
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 · 35 lines · 44 tokens per session scan A 88cde2ffaff3
trend-spotter is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 44 tokens to every session and 378 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-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.