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/vfxprojoe/studiosignal-plugin/research-frameworksnpx skills add vfxprojoe/studiosignal-plugin --skill research-frameworksgit clone --depth 1 https://github.com/vfxprojoe/studiosignal-pluginWhat 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.00047 | $0.01039 |
| Opus 5 | $0.00023 | $0.00519 |
| Sonnet 5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
research-frameworks 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
M&E Research Frameworks
Studio Signal auto-selects the best framework server-side when you call ask_kai. Your job is to phrase queries clearly so the right framework activates. Prefer ask_kai for grounded analysis — do not substitute your own unsourced framework write-ups.
Query phrasing guide (critical)
| User intent | Example query to pass to ask_kai |
Framework activated |
|---|---|---|
| Head-to-head vendor/product comparison | "Competitor research: Signiant vs IBM Aspera vs Media Shuttle" | competitive (NOT SWOT) |
| Single-company positioning | "Analyze Frame.io's market positioning and ideal buyer profile" | competitive |
| Explicit SWOT/TOWS | "SWOT analysis of Warner Bros Discovery" | swot |
| Moats / durable advantage | "Does Spotify have a durable competitive advantage?" | sevenpowers |
| Industry structure | "Porter's Five Forces in the FAST channel market" | porters |
| Earnings / stock | "Disney Q2 earnings breakdown with key metrics" | financial |
| FAST / AVOD / CTV ads | "FAST and CTV ad economics — CPM and fill rate trends" | adeconomics |
| Creator M&A | "Creator economy M&A — recent MCN and creator-studio deals" | creatorma |
| AI disruption | "How is AI affecting localization vendors?" | aiimpact |
Do NOT say "SWOT" or "TOWS" for competitor bake-offs — say "competitor research" or "head-to-head comparison" instead.
Framework catalog (30+)
Comparison & strategy
- competitive — Battlecard / head-to-head product & vendor comparisons (B2B media-tech, workflow tools)
- swot — SWOT/TOWS (only when user explicitly requests SWOT)
- porters — Five Forces (industry structure, not product bake-offs)
- sevenpowers — Hamilton Helmer 7 Powers (single-company moats)
- bcg — Growth-Share Matrix
- pestle — Macro factor scan
- disruption — Christensen disruption theory
- scenario — Bull/base/bear futures
- blueocean — Value innovation (explicit request)
- growth — Ansoff matrix (explicit request)
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.
- 2d ago First seen · 82 lines · 47 tokens per session scan A 684dcd6b0477
research-frameworks is a skill published in the GitHub repository vfxprojoe/studiosignal-plugin (2 stars, last pushed 21d ago), licensed MIT. It adds 47 tokens to every session and 1,039 once invoked, about $0.0002 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-31.
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…