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 commands/jxxh204/streamdeck-mcp/taskgit clone --depth 1 https://github.com/jxxh204/streamdeck-mcpWhat 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.00023 | $0.01913 |
| Opus 5 | $0.00012 | $0.00957 |
| Sonnet 5 | $0.00005 | $0.00383 |
| Haiku 4.5 | $0.00002 | $0.00191 |
Grade A, and why
task 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 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.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Context Setup
Collects context from Notion, Slack, and GitHub for a task and sets up a Stream Deck folder with quick-access links.
Input
$ARGUMENTS — one of:
- Task ID (e.g.
PROJ-123) → Notion-centric search - Slack thread URL (e.g.
https://yourworkspace.slack.com/archives/...) → extract context from thread - Free text (e.g.
PR review cleanup) → simple task folder with text only clearorclear N→ clear all or specific slot- Empty → auto-detect task ID from current git branch
Input type detection
- Matches
[A-Z]+-\d+pattern → Type 1: Notion search - Contains
slack.comorslackMessage://→ Type 2: Slack thread - Matches
clearorclear N→ Type 0: Clear folder - Otherwise → Type 3: Free text
- Empty → extract task ID from current git branch, then Type 1
Prerequisites
You must pre-create folder slots in the Elgato Stream Deck app (programmatic folder creation is not supported by the Elgato app).
- In the Elgato Stream Deck app, create empty folders on your target profile's task page
- Call
streamdeck_read_pageto read that page and note each folder button'saction_idand theProfileUUIDin itsSettings - Store this mapping below — the skill will reuse it for every
/taskinvocation
Slot mapping (customize for your setup)
Replace the placeholders with your own values:
Profile name: YOUR_PROFILE_NAME
Task page directory_id: YOUR_PAGE_DIRECTORY_ID
Folder slots:
| Slot | Key | action_id | ProfileUUID |
|------|-----|------------------|-------------------|
| 1 | 0 | <action_id> | <ProfileUUID> |
| 2 | 1 | <action_id> | <ProfileUUID> |
| 3 | 2 | <action_id> | <ProfileUUID> |
| 4 | 3 | <action_id> | <ProfileUUID> |
Each folder's child page directory_id is the ProfileUUID in UPPERCASE.
Type 0: clear — empty a folder
/task clear → empty all folders
/task clear 1 → empty slot 1 only
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 · 190 lines · 23 tokens per session scan A 51fa3ff16f0c
task is a command published in the GitHub repository jxxh204/streamdeck-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,913 once invoked, about $0.0001 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).