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/zookanalytics/gc-toolkit/gc-demo-scriptnpx skills add zookanalytics/gc-toolkit --skill gc-demo-scriptgit clone --depth 1 https://github.com/zookanalytics/gc-toolkitWrote 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/zookanalytics/gc-toolkit/gc-demo-script)<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/gc-demo-script"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/gc-demo-script.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.00031 | $0.04310 |
| Opus 5 | $0.00015 | $0.02155 |
| Sonnet 5 | $0.00006 | $0.00862 |
| Haiku 4.5 | $0.00003 | $0.00431 |
Grade A, and why
gc-demo-script 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GC Demo Script — Gas City Bead to Demo Script
Generate a demo:capture-format markdown script from a completed Gas City
work bead.
This skill is the Gas City-native sibling of demo:epic: it reads the bead
description, notes, parent molecule, sibling design-leg beads, and git/PR
diff, then produces a user-facing demo script that demo:capture can
execute.
This skill DOES NOT run demo:capture. It writes a script file and
returns the path.
The caller (human or another skill) invokes demo:capture separately on the
generated script.
This matches demo:epic's separation between generation and execution.
When to use
Use this skill when:
- A Gas City work bead is closed (usually with a merged or open PR)
- You want a user-facing demo of what the bead's work actually changed
- The bead does NOT have BMAD artifacts (use
demo:epicfor BMAD-driven work that lives under_bmad-output/)
Input
You receive parsed arguments from the command wrapper:
- Bead ID (required) — e.g.,
sl-8jv --pr <number>(optional) — PR number, otherwise derived frommetadata.pr_numberon the bead--focus "area"(optional) — bias the demo narration toward a specific functional area (e.g., "mobile", "diff viewing")
If no bead ID is provided, ask the caller for one.
Prerequisites Check
Before gathering context, verify:
bdCLI is available —command -v bdsucceeds- Bead exists —
bd show <id>returns a valid result
If the bead doesn't exist, stop and report:
"Bead <id> not found. Check the ID and try again."
Unlike demo:epic, this skill does NOT require Playwright MCP, ImageMagick,
or a running app — it only generates a script file.
The script can be executed later by demo:capture from a session that has
those prerequisites.
Phase A: Gather Context (sequential reads)
Gas City sources are interconnected — the work bead references sibling design-leg beads, parent molecules, and commits. Read them in order; do NOT dispatch parallel subagents (the inputs are small enough for direct reads, and ordering matters for cross-references).
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 · 455 lines · 31 tokens per session scan A 14e48d18c940
gc-demo-script is a skill published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 4,310 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.
Other skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
error-recovery
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
agentic-workflow-designer
Conversational skill that interviews users to design new agentic workflows.
security-review
How to review PRs for security — credentials, injection, workflow permissions, supply chain, git operation safety.
shogun-screenshot
スクリーンショットの取得・加工を行う。ローカルスクショから最新画像を取得、 PlaywrightでWebページをキャプチャ、画像のトリミング・リサイズ、機微情報を黒塗りマスキング。 記事執筆、レポート作成、UI確認、画像加工時に起動。 「スクショ」「スクリーンショット」「画面キャプチャ」「最新のスクショ」「画像加工」「トリミング」「マスク」「写メ」「写メ撮った」「スクショ撮った」で起動。 Do NOT use for: 画像生成（shogun-imagegenを使え）。.