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/ambient-code/platform/cypress-demonpx skills add ambient-code/platform --skill cypress-demogit clone --depth 1 https://github.com/ambient-code/platformWhat 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.00076 | $0.00889 |
| Opus 5 | $0.00038 | $0.00445 |
| Sonnet 5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
cypress-demo scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Verify the frontend is accessible: `curl -s -o /dev/null -w "%{http_code}" http://localhost:3000` How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cypress Demo
Create a polished Cypress demo test that records a human-paced video walkthrough of UI features on the current branch.
Usage
/cypress-demo # Auto-detect features from branch diff
/cypress-demo chat input refactoring # Describe what to demo
User Input
$ARGUMENTS
Behavior
When invoked, create a Cypress test file in e2e/cypress/e2e/ that records a demo video with:
- Synthetic cursor (white dot) that glides smoothly to each interaction target
- Click ripple (blue expanding ring) on every click action
- Caption bar (compact dark bar at top of viewport) describing each step
- Human-paced timing so every action is clearly visible
--no-runner-uiflag to exclude the Cypress sidebar from the recording
1. Determine what to demo
- If
$ARGUMENTSis provided, use it as the demo description - If empty, run
git diff main..HEAD --statto identify changed files and infer features - Read the changed/new component files to understand what UI to showcase
- Ask the user if clarification is needed
2. Check prerequisites
- Verify
e2e/.env.testore2e/.envexists withTEST_TOKEN - Check if
ANTHROPIC_API_KEYis available (needed for Running state) - Verify the kind cluster is up:
kubectl get pods -n ambient-code - Verify the frontend is accessible:
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000
3. Create the demo test file
Create e2e/cypress/e2e/<feature-name>-demo.cy.ts using the helpers below.
Required helpers
Each demo file must define the following helpers inline (they are not shared utilities — embed them directly in the test file):
- Functions:
caption(),clearCaption(),initCursor(),moveTo(),moveToText(),clickEffect(),cursorClickText() - Timing constants:
LONG,PAUSE,SHORT,TYPE_DELAY
See the patterns table below for usage. If a prior demo file already exists in e2e/cypress/e2e/, copy the helpers from there; otherwise implement them fresh using the patterns below.
What ships with it
1 file 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.
- 2d ago First seen · 86 lines · 76 tokens per session scan A c0abc22eb26c
cypress-demo is a skill published in the GitHub repository ambient-code/platform (129 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 889 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
company-hiring-intelligence
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence, figure out a tech stack from job…
文档协作
引导用户通过结构化的文档共同编写工作流程。当用户想撰写文档、提案、技术规范、决策文档或类似结构化内容时使用。该工作流程帮助用户高效传递上下文，通过迭代优化内容，并验证文档对读者有效。当用户提到写文档、创建提案、起草规范或类似文档任务时触发。.
aidd-dev:08:for-sure
Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…