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 gaelic-ghost/socket --skill mainstage-workflowgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/mainstage-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/mainstage-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/mainstage-workflow/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/gaelic-ghost/socket/mainstage-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/mainstage-workflow.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.00061 | $0.00617 |
| Opus 5.5 | $0.00024 | $0.00247 |
| Sonnet 5.5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
mainstage-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 1mo 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MainStage Workflow
Use this skill for MainStage app operation and rehearsal preparation. Treat an active performance configuration as high risk.
Source Check
Search the local Tips/Help Viewer catalog for MainStage or open MainStage Help. Confirm the guide matches the installed app/version. Read references/concert-safety-contract.md before changing concert, set, patch, device, mapping, playback, or recording state.
Workflow
- Classify the request: inspect, rehearsal preparation, concert/set/patch organization, audio/MIDI device setup, channel-strip routing, mapping, missing device/plug-in repair, backup, or live-performance issue.
- Establish the performance contract: whether the configuration is live, rehearsal-only, or disposable; available audio/MIDI hardware; intended inputs/outputs; selected concert/set/patch; backup location; and what must not change.
- Inspect before action: active mode, selected set/patch, concert path, audio device, MIDI devices/controllers, channel strips, output routing, mappings, missing plug-ins/media, and current playback/record state.
- Preserve the concert. For configuration changes, use a duplicate or explicit backup. Do not save over an active performance file without confirmation.
- Confirm immediately before changing selected patches, audio or MIDI devices, channel-strip output routes, mappings, playback, recording, or concert file state. State the user-visible effect and recovery path.
- Prepare one rehearsal path: verify audio input/output, MIDI response, patch selection, mappings, level/mute behavior, and any backing-track/transport behavior using observed device evidence.
- Report the ready/not-ready state with the specific concert/set/patch, connected devices, tested routes, untested components, backup status, and next safe action.
Guards
- Never validate against a live show without explicit confirmation at the moment of the potentially disruptive action.
- Do not change a concert, patch, mapping, or audio/MIDI device merely to see what happens.
- Do not claim hardware routing, controller response, latency, or sound-check readiness without observed device evidence.
- Do not perform unattended playback, recording, or device reconfiguration.
- Do not treat missing plug-ins/media as something to replace automatically; identify the exact dependency and stop for direction.
What ships with it
2 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.
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.
- 1mo ago First seen · 37 lines · 61 tokens per session scan A 1dd227429293
mainstage-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 617 once invoked, about $0.0002 per session on Opus 5.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
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…
pipeline-auto
Use when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
fast-pipeline
Use when the user wants a feature built quickly with low token cost and few interruptions, approves a spec once, and says no automated tests should be written because they will test it manually — "fast pipeline", "go fast, no tests, I'll test it myself", "don't keep asking me". Not for a run that should write or keep…