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/heygen-com/heygen-cli/e2e-cli-testnpx skills add heygen-com/heygen-cli --skill e2e-cli-testgit clone --depth 1 https://github.com/heygen-com/heygen-cliWhat 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.00071 | $0.02290 |
| Opus 5 | $0.00036 | $0.01145 |
| Sonnet 5 | $0.00014 | $0.00458 |
| Haiku 4.5 | $0.00007 | $0.00229 |
Grade A, and why
e2e-cli-test 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 2d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E CLI Test
Pre-release validation that exercises ./bin/heygen against the live HeyGen API.
Prerequisites
HEYGEN_API_KEYmust be set in the environment- Working directory must be the heygen-cli repo root
Workflow
Run each phase in order. Report results as you go. If a phase fails, continue
to the next phase (do not abort early) so the final report covers everything.
Always use ./bin/heygen (the freshly built binary), never a globally installed heygen.
Step 1: Build
make build
If this fails, stop and report the build error. Nothing else can run.
Step 2: Phase 1 -- Auth and account
./bin/heygen auth status
./bin/heygen user me get
- Assert
auth statusexits 0 - Assert
user me getexits 0, stdout is valid JSON, andjq -e '.data.username'succeeds - If either command fails, stop and report the auth error. Every subsequent phase requires a valid key.
Step 3: Phase 2 -- Read-only list commands
Run each command below. Assert exit 0 and valid JSON stdout for every one. Save the JSON output from each -- Phase 3 will extract IDs from these results.
./bin/heygen video list --limit 1
./bin/heygen template list --limit 1
./bin/heygen ai-clipping list --limit 1
./bin/heygen avatar list --limit 1
./bin/heygen avatar looks list --limit 1
./bin/heygen voice list --limit 1
./bin/heygen audio sounds list --query "calm ambient piano" --limit 1
./bin/heygen video-translate list --limit 1
./bin/heygen video-translate languages list
./bin/heygen video-agent list --limit 1
./bin/heygen video-agent styles list --limit 1
./bin/heygen lipsync list --limit 1
./bin/heygen webhook endpoints list
./bin/heygen webhook event-types list
./bin/heygen webhook events list
./bin/heygen brand kits list --limit 1
./bin/heygen brand glossaries list --limit 1
asset list requires --username (the workspace member whose assets to list,
the owner value on asset items) while the endpoint is in beta. Use the
.data.username captured in Phase 1 (user me get):
./bin/heygen asset list --username <phase-1-username> --limit 1.
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.
- 2d ago First seen · 217 lines · 71 tokens per session scan A ec8445d187bf
e2e-cli-test is a skill published in the GitHub repository heygen-com/heygen-cli (113 stars, last pushed 3d ago), licensed Apache-2.0. It adds 71 tokens to every session and 2,290 once invoked, about $0.0004 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-30.
Other skills, from other repositories
presentation
Turn a tech-spec directory into an interactive, marketing-grade web presentation — built so engineers understand the design, the reader is convinced of the why, and the result is shareable in public. Use when someone wants a spec turned into a deck.
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
iii-core-primitives
Use when registering iii functions, binding triggers, selecting sync/void/enqueue invocation, creating workers, inspecting the live worker registry, installing registry workers, authoring custom triggers, moving channel data, or adapting external HTTP functions across TypeScript, Python, and Rust.