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/daily-workflownpx skills add vfxprojoe/studiosignal-plugin --skill daily-workflowgit clone --depth 1 https://github.com/vfxprojoe/studiosignal-pluginWrote 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/vfxprojoe/studiosignal-plugin/daily-workflow)<a href="https://agentmods.dev/skills/vfxprojoe/studiosignal-plugin/daily-workflow"><img src="https://agentmods.dev/badge/skills/vfxprojoe/studiosignal-plugin/daily-workflow.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.00504 |
| Opus 5 | $0.00026 | $0.00252 |
| Sonnet 5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
daily-workflow 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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily M&E Intelligence Workflow
When the user asks for daily M&E intelligence, follow this workflow using the Studio Signal MCP tools. This gives them a comprehensive morning briefing experience.
Workflow Steps
1. Fetch the Daily Brief
Call get_daily_brief to retrieve today's executive intelligence brief. This is generated every morning before market open and includes:
- Top M&E stories ranked by strategic impact
- Market movers and stock movements
- Key themes and trends
- Watch list items
Present the brief with clear formatting — headlines, impact assessments, and market data.
2. Check Market Data
Call get_stocks to get current M&E sector stock data. Highlight:
- Biggest movers (up and down) among the 30+ tracked M&E stocks
- Any stocks mentioned in the daily brief
- Overall sector trend vs. broader market
3. Offer the Deep Dive
After presenting the brief and market overview, offer to fetch the deep dive analysis using get_deep_dive. The deep dive expands on the morning brief's most impactful story with:
- Comprehensive strategic analysis
- Competitive implications
- Market outlook and recommendations
4. Follow-Up Research
Based on the brief and deep dive, suggest specific research questions the user might want to explore via ask_kai. For example:
- "Want me to do a deep analysis of [company mentioned in brief]?"
- "Should I look at the competitive implications of [deal/event from brief]?"
- "Want me to pull the earnings details for [company that moved significantly]?"
Presentation Guidelines
- Lead with the most impactful story — don't bury the lead
- Use the stock data to add quantitative context to qualitative stories
- Connect dots between stories when themes overlap
- Always mention if the daily podcast is available
- End with actionable follow-up options
Trigger Phrases
Activate this workflow when the user says things like:
- "What's happening in M&E today?"
- "Give me today's brief"
- "Morning briefing"
- "Daily intel"
- "What did I miss in media today?"
- "Catch me up on entertainment news"
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.
- 4d ago First seen · 58 lines · 51 tokens per session scan A b0ed3ee4e4d6
daily-workflow is a skill published in the GitHub repository vfxprojoe/studiosignal-plugin (2 stars, last pushed 23d ago), licensed MIT. It adds 51 tokens to every session and 504 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-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…