cue-programming

cue-programming is a skill for Claude Code from drohi-r/beyond-mcp. It costs 45 tokens per session (948 once invoked), scanned A, original, Apache-2.0.

A show-control toolset for BEYOND, software used to run live audiovisual shows. It helps operators organize, select, start, pause, restart, and stop cues, which are timed actions or media events.

In plain words
What is it for?
Building and running cue sequences, switching between pages or tabs, navigating the cue grid, and controlling cue playback during live events.
Why use it?
It reduces the need to manage live cues manually while navigating many pages, tabs, and cue-grid cells during a show.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Install

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.

agentmods
npx agentmods add skills/drohi-r/beyond-mcp/cue-programming
Any agent
npx skills add drohi-r/beyond-mcp --skill cue-programming
Clone the repo
git clone --depth 1 https://github.com/drohi-r/beyond-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for cue-programming

README.md
[![agentmods](https://agentmods.dev/badge/skills/drohi-r/beyond-mcp/cue-programming.svg)](https://agentmods.dev/skills/drohi-r/beyond-mcp/cue-programming)
Your own site
<a href="https://agentmods.dev/skills/drohi-r/beyond-mcp/cue-programming"><img src="https://agentmods.dev/badge/skills/drohi-r/beyond-mcp/cue-programming.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 948 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00948
Opus 5 $0.00023 $0.00474
Sonnet 5 $0.00009 $0.00190
Haiku 4.5 $0.00005 $0.00095

Measured 6d ago against content hash 43a197cf1470, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

cue-programming 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 6d 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.

.claude/skills/cue-programming/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cue Programming

Use this skill when the operator needs to build or manage cue sequences, trigger cues, navigate the cue grid, or set up pages and tabs for a show.

Workflow — Building a cue sequence

  1. Navigate to the right page/tab.

    • select_page index — jump to a page
    • select_tab_by_name name — or select tab by name
    • select_category_by_name name — filter by content category
  2. Focus and trigger cues.

    • focus_cell page, cue — focus on a specific cell
    • start_cell — start the focused cell
    • Or use name-based: start_cue_by_name name
  3. Control playback.

    • pause_cue page, cue, 1 — pause a running cue
    • pause_cue page, cue, 0 — unpause
    • restart_cue page, cue — restart from beginning
    • stop_cue_now page, cue — immediate stop
    • stop_cue_sync page, cue, fade — stop with fade
  4. Navigate cue grid.

    • cue_down / cue_up — move selection
    • shift_focus direction — shift by offset
    • move_focus dx, dy — move by delta
    • focus_cell_index index — jump to linear position
  5. Set cue mode for the situation.

    • set_cue_mode_single — one cue at a time (safe for busking)
    • set_cue_mode_one_per — one per group (layer-based)
    • set_cue_mode_multi — multiple simultaneous (complex shows)

Workflow — Live show operation

  1. Set click behavior for the session.

    • click_mode_select — standard selection
    • click_mode_flash — momentary trigger
    • click_mode_toggle — toggle on/off
    • click_mode_live — live performance mode
  2. Set transitions.

    • set_transition_type index — select transition effect
    • set_master_transition_time seconds — set crossfade duration
  3. Trigger cues by name.

    • start_cue_by_name "intro_beams"
    • start_cue_by_name "verse_tunnels"
    • stop_cue_by_name "intro_beams"
  4. Quick stop.

    • unselect_all_cues — deselect everything
    • stop_all_sync fade — graceful stop with fade
    • stop_all_now — emergency stop (destructive)

Read the full file on GitHub · 102 lines

Changes

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.

  1. 6d ago First seen · 102 lines · 45 tokens per session scan A 43a197cf1470

Subscribe to this mod's changes

cue-programming is a skill published in the GitHub repository drohi-r/beyond-mcp (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 948 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.

Related

Other skills, from other repositories

openSUSE-packaging

Authoring, modifying, reviewing, or building openSUSE RPM packages — spec files, .changes files, osc / OBS and Git (src.opensuse.org / Gitea) workflows. Use whenever the working directory has a .osc/ folder or a .spec file, when the user mentions osc, OBS, rpmbuild, openSUSE Build Service, src.opensuse.org, the Git…

openSUSE/openSUSE-packaging-skill · 195 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens