record-demo

record-demo is a skill for Claude Code from apify/mcpc. It costs 114 tokens per session (3,679 once invoked), scanned B, original, Apache-2.0.

Instructions for recording terminal demonstrations of mcpc as animated GIF files using VHS. VHS runs a scripted shell session, types real commands, captures the terminal, and renders the animation.

In plain words
What is it for?
Use it to create or update the mcpc README demo and focused VHS tapes in docs/vhs. It covers flows such as listing sessions, inspecting tools, connecting to servers, and running a tool call.
Why use it?
It keeps the demo reproducible and helps avoid errors in timing, authentication, command output, or formatting. The tapes show how mcpc connects to local and remote MCP servers and calls their tools.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is cp mcpc-demo.gif ../images/mcpc-demo.gif # update the README hero.

Good fit Use it to create or update the mcpc README demo and focused VHS tapes in docs/vhs. It covers flows such as listing sessions, inspecting tools, connecting to servers, and running a tool call.

Compare 6 skills from other repositories ↓
About the project

mcpc is a command-line client for the Model Context Protocol, giving shell commands access to MCP servers' tools, resources, prompts, skills, and other operations. Developers and AI agents use it to inspect, debug, and script MCP workflows through standard shell pipelines, with the catalogue add-ons supporting its use in agent workflows.

apify/mcpc · 1,081 stars · on GitHub · npmjs.com

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/apify/mcpc
agentmods
npx agentmods add skills/apify/mcpc/record-demo

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 record-demo

README.md
[![agentmods](https://agentmods.dev/badge/skills/apify/mcpc/record-demo/github.svg)](https://agentmods.dev/skills/apify/mcpc/record-demo)
Your own site
<a href="https://agentmods.dev/skills/apify/mcpc/record-demo"><img src="https://agentmods.dev/badge/skills/apify/mcpc/record-demo/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.

agentmods 80×15 button for record-demo

Your own site · 80×15
<a href="https://agentmods.dev/skills/apify/mcpc/record-demo"><img src="https://agentmods.dev/badge/skills/apify/mcpc/record-demo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,679 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00114 $0.03679
Opus 5.5 $0.00046 $0.01472
Sonnet 5.5 $0.00023 $0.00736
Haiku 4.5 $0.00011 $0.00368

Measured 1mo ago against content hash 4b18cebb0d9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

record-demo scanned grade B with 1 finding 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

| `security.tape` | Auto-discovery skipping a checked-in `.mcp.json` entry that reads `${GITHUB_TOKEN}` (fixture: `security.mcp.json`, copied into a `mktemp -d` HOME so no real configs are discovered); needs `mcp.example
skills/record-demo/SKILL.md · 238 lines

How it starts

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

record-demo: VHS demo GIFs for mcpc

The tapes in docs/vhs/*.tape are VHS scripts that drive a real shell session — VHS types each command, runs it against a live MCP server, captures the terminal, and renders a GIF. The README hero is docs/images/mcpc-demo.gif, built from docs/vhs/mcpc-demo.tape.

This file is the accumulated know-how. Read all of it before touching a tape — most rules below were discovered by hitting the wall, and skipping them wastes whole render cycles (~1–2 min each).

The hero flow (mcpc-demo.tape)

A basic-use story across both transports:

  1. mcpc — empty state (no sessions, no profiles)
  2. mcpc connect mcp.json:filesystem — local stdio server (auto-names @filesystem)
  3. mcpc — session list (now shows the live session)
  4. mcpc @filesystem tools-list
  5. mcpc @filesystem tools-list --json — JSON output, syntax-highlighted, no jq
  6. mcpc connect mcp.apify.com -H "Authorization: Bearer $APIFY_TOKEN" — remote HTTP server (auto-names @apify)
  7. mcpc @apify tools-list
  8. mcpc @apify tools-get search-actors — inspect one tool's input schema
  9. mcpc @apify tools-call search-actors keywords:="web scraper" limit:=3
  10. mcpc @apify close

Ten commands run ~45s; there is no hard 30s cap for this flow.

Style conventions (the current standard — match these)

  • No # comments in the visible script. The commands are self-descriptive.
  • No | head, no 2>/dev/null on visible commands. Show real output even if long — it scrolls naturally. (connect ≈ 86 lines incl. an "Available commands" list, tools-call search-actors ≈ 56, filesystem tools-list --json ≈ 300.)
  • Continuous session — never clear between steps. Put a single blank-line Enter before each command (after the first) so it's separated from the previous output, like a real terminal session.
  • Colored prompt + bold-white typed commands. In the hidden setup block:
    Type 'export PS1="\[\e[1;38;2;25;230;77m\]$\[\e[0m\] \[\e[1;97m\]"'
    Enter
    Type "trap 'tput sgr0' DEBUG"
    Enter
    
    • PS1 is a bold bright-green $, then ends with \[\e[1;97m\] so the typed input renders bold bright-white.
    • The DEBUG trap runs tput sgr0 before every command so the bold-white input does not bleed into command output.
  • Empty state needs a clean home — hidden: Type 'export MCPC_HOME_DIR="$(mktemp -d)"' so mcpc shows "No active MCP sessions / No OAuth profiles".
  • Color is automatic for non-piped commands — mcpc detects the TTY and emits color (256-color, plenty vivid). You only need export FORCE_COLOR=3 (+ COLORTERM=truecolor for exact hex) when a command is piped (mcpc turns color off when stdout isn't a TTY). The current tapes avoid pipes, so they don't need it. (The CLI palette lives in src/cli/output.ts, RAINBOW_SATURATION, bumped to 78% for vividness — that's where the demo colors come from.)

Read the full file on GitHub · 238 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. 1mo ago Changed · +21 lines scan A → B 4b18cebb0d9d
  2. 2mo ago First seen · 217 lines · 114 tokens per session scan A 4fcb08ff7eca

Subscribe to this mod's changes

record-demo is a skill published in the GitHub repository apify/mcpc (1,081 stars, last pushed yesterday), licensed Apache-2.0. It adds 114 tokens to every session and 3,679 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.