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/ccplugins/awesome-claude-code-plugins/market-pulsenpx skills add ccplugins/awesome-claude-code-plugins --skill market-pulsegit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWhat 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.00061 | $0.00644 |
| Opus 5 | $0.00030 | $0.00322 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
market-pulse 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market pulse
Answer "what's happening right now?" from AlphaAI's feed. Two tools cover two different questions — pick the right one:
alphai_actionable_now— breaking, decision-grade news from the last few hours. The gate is strict: by default onlyactionability='high'(something to act on TODAY — guidance cut, halted trading, breaking M&A, surprise print).alphai_trending— top stories of the last 48h by relevance. The "big picture", not necessarily urgent.
Steps
- Start narrow, with
alphai_actionable_now()(defaults: last 6h, high-actionability). This is the real "is anything breaking" signal. - Read an empty result correctly. Outside major market hours (nights,
weekends — crypto trades 24/7, but high-actionability prints still cluster in
US/European/Asian sessions) an empty list is expected — it means no
high-actionability prints in the window, not that the tool failed. Before
concluding "nothing happened", widen once:
alphai_actionable_now(hours=24, min_actionability='medium'). - Add the backdrop with
alphai_trending(limit=10). Use this for the "bigger stories shaping the week" layer even when nothing is breaking. - Optional focus. If the user named a sector or theme, resolve it to
tickers (
alphai_tickers(q=...)or your own knowledge), thenalphai_news_search(tickers=[...], min_relevance=7)— there is no free-text news search; match themes client-side on the returned titles/summaries.
Output
- Breaking now — the high-actionability items, if any. Each: headline · ticker(s) · one clause on the decision it forces. If none, say so in one line and note the window you checked.
- Big picture — 3–5 trending stories by relevance, each a one-liner.
- So what — one or two sentences tying it together (risk-on/off, a sector in focus, an event everyone's positioning around).
Guardrails
- Don't conflate "trending" with "actionable". A story can dominate the tape (trending) without being something to act on today (actionable). Label which layer each item came from if it matters.
- Report relevance / actionability honestly; don't upgrade a medium item to "breaking".
- News, not advice — no trade calls.
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 · 50 lines · 61 tokens per session scan A 0d143ed7adf3
market-pulse is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (929 stars, last pushed 21d ago), licensed Apache-2.0. It adds 61 tokens to every session and 644 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 skills, from other repositories
e2e-test-skill
E2E test skill for validation.
dynamic-workflow-patterns
Pattern taxonomy, agent role combinations, model routing, unit-of-work sizing, review-findings settling, and resilience discipline for Claude Code dynamic workflows. ALWAYS load this skill before authoring or running any Workflow tool script, and ALWAYS load it when the user mentions "workflow" or "ultracode" in any…
serena-tool-selection
MANDATORY tool selection protocol for Serena LSP tools vs Claude Code built-in tools. ALWAYS use when your tools list includes any mcpserena tools. This skill OVERRIDES default tool selection behavior for code navigation tasks.
diagram-drawio
Skill "diagram-drawio" from lc-semba-ryuichiro/semba-claude-plugins, covering draw\.io図作成ガイドライン, 目次, 事前準備チェックリスト, 図の設計原則 and 段階的開示（progressive disclosure）.
webpify
Skill "webpify" from lc-semba-ryuichiro/semba-claude-plugins, covering webpify 使用ガイド, 目次, 概要, 事前準備チェックリスト and 実行方法.
atl-fetch-confluence
Skill "atl-fetch-confluence" from lc-semba-ryuichiro/semba-claude-plugins, covering confluence 情報取得ガイド, 目次, 概要, 事前準備チェックリスト and 実行方法.