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/stock-briefnpx skills add ccplugins/awesome-claude-code-plugins --skill stock-briefgit 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.00077 | $0.00604 |
| Opus 5 | $0.00039 | $0.00302 |
| Sonnet 5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
stock-brief 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stock brief
Give a tight, decision-useful read on one ticker from AlphaAI's enriched feed. Not a price quote — a news brief: what's been happening, who's buying or selling, and what to keep an eye on.
Steps
- Resolve the ticker. If the user gave a company name, not a symbol, call
alphai_tickers(q=...)to find it. Ifalphai_ticker_newsreturnsunknown_ticker=true, tell the user and stop — don't invent coverage. - Pull the ticker feed. Call
alphai_ticker_news(ticker, collapse_stories=true).collapse_storiesfolds syndicated reprints into one row each and adds asources_countcorroboration signal — prefer it for a clean brief. Insider news is included by default; keep it. - Optional context. If the user wants the wider tape, call
alphai_trending(limit=5)and note any market-level story that touches this name or its sector. - Deep-dive on demand. If one story clearly drives the brief and the user
wants detail, fetch it with
alphai_article(uid)for the full enrichment (ticker analysis, key entities). The article body is not served — work from the enrichment and summary.
Output
Keep it to a screen. Structure:
- One-line read — the single most important thing about this name right now.
- Top stories — 3–5 bullets, each: headline · relevance score · one-clause
"why it matters". Lead with the highest
relevance_score. - Insider activity — any Form 4 / 13F rows from the feed: who, buy or sell, size if given. "No notable insider activity in the window" is a valid line.
- Watch next — 1–2 concrete things that would change the picture.
Guardrails
- Every story carries a 1–10
relevance_score; lead with the high ones and say the score so the user can calibrate. - This is news, not advice. Don't issue buy/sell calls or price targets — summarize what the reporting says and let the user decide.
- If the feed is thin, say so plainly rather than padding. A short honest brief beats a long speculative one.
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 · 48 lines · 77 tokens per session scan A 4a13a82a3483
stock-brief 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 77 tokens to every session and 604 once invoked, about $0.0004 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 実行方法.