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 Security-Phoenix-demo/security-skills-claude-code --skill phoenix-research-pipelinegit clone --depth 1 https://github.com/Security-Phoenix-demo/security-skills-claude-codeWrote 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/security-phoenix-demo/security-skills-claude-code/phoenix-research-pipeline)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-research-pipeline"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-research-pipeline/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/security-phoenix-demo/security-skills-claude-code/phoenix-research-pipeline"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-research-pipeline.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.00173 | $0.02072 |
| Opus 5 | $0.00086 | $0.01036 |
| Sonnet 5 | $0.00035 | $0.00414 |
| Haiku 4.5 | $0.00017 | $0.00207 |
Grade A, and why
phoenix-research-pipeline scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Installs: yt-dlp, scrapling, notebooklm-py, notebooklm-cli, praw, requests, curl-cffi, browserforge How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix Security Research Pipeline
Automated research → quality filtering → NotebookLM ingestion with Phoenix brand prompts.
Quick Start
# Interactive (prompts for topic)
python3 scripts/research_pipeline.py
# Full pipeline: YouTube + web + NotebookLM
python3 scripts/research_pipeline.py "CISA KEV exploited vulnerabilities 2025" \
--count 25 --notebooklm --prompt blog
# YouTube only
python3 scripts/youtube_research.py "container security kubernetes" --count 25
# Web only (Brave primary, Scrapling fallback)
python3 scripts/web_research.py "ASPM application security posture" --count 20 --reddit
# Push URLs directly to NotebookLM
python3 scripts/notebooklm_push.py --urls urls.txt --title "My Research" \
--backend teng --prompt slides
CRITICAL: Authentication Required
NotebookLM requires Google auth. Before first use, tell the user:
"Open a separate terminal and run:
notebooklm loginThis will open a browser for Google authentication. Come back when it completes."
This must happen before any --notebooklm flag will work.
Workflow
User gives topic (or Claude asks)
↓
[1] YouTube Research (yt-dlp) — metadata: title, views, channel, duration, URL
[2] Web Research (Brave → Scrapling fallback) — title, URL, description, quality score
[3] Reddit Research (optional flag) — top posts from security subreddits
↓
Quality Filter (min score 5/10 default, configurable)
Deduplication
↓
[4] NotebookLM Push — all URLs → new notebook → Phoenix prompt → analysis
↓
Summary: sources ingested, notebook URL, analysis preview
Claude Behaviour
When a user gives a research command:
- Extract topic — if none given, ask: "What topic do you want to research?"
- Run pipeline using
bash_tool:cd /path/to/skill && python3 scripts/research_pipeline.py "TOPIC" \ --count 25 --notebooklm --prompt blog - Check auth — if NotebookLM fails with auth error, show login instruction
- Report results — paste the summary output; include notebook URL
- Offer next steps — "Want slides or a video script version? Re-run with
--prompt slides"
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/brand.md 6.3 KB
- references/prompts.md 2.7 KB
- scripts/install.sh 4.2 KB runs code
- scripts/notebooklm_push.py 11 KB runs code
- scripts/pipeline.py 9.3 KB runs code
- scripts/research_pipeline.py 7.2 KB runs code
- scripts/web_research.py 9.1 KB runs code
- scripts/youtube_research.py 3.5 KB runs code
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.
- yesterday First seen · 242 lines · 173 tokens per session scan A b05109c18a34
phoenix-research-pipeline is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 173 tokens to every session and 2,072 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…