Borrowing it
Nothing to install: this file belongs to yfge/ai-video-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yfge/ai-video-studio/main/.codex/skills/ai-video-studio-frontend-test/SKILL.mdgit clone --depth 1 https://github.com/yfge/ai-video-studioWrote 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/yfge/ai-video-studio/ai-video-studio-frontend-test)<a href="https://agentmods.dev/skills/yfge/ai-video-studio/ai-video-studio-frontend-test"><img src="https://agentmods.dev/badge/skills/yfge/ai-video-studio/ai-video-studio-frontend-test/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.
<a href="https://agentmods.dev/skills/yfge/ai-video-studio/ai-video-studio-frontend-test"><img src="https://agentmods.dev/badge/skills/yfge/ai-video-studio/ai-video-studio-frontend-test.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00083 | $0.00558 |
| Opus 5 | $0.00042 | $0.00279 |
| Sonnet 5 | $0.00017 | $0.00112 |
| Haiku 4.5 | $0.00008 | $0.00056 |
Grade A, and why
ai-video-studio-frontend-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 11d 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.
What it actually says
AI Video Studio Frontend Test
Use this skill to decide the right frontend validation depth without diluting the minimum gate. npm run lint is the baseline; npm run test and npm run build are added when the change risk justifies them.
Read First
AGENTS.mddocs/testing/agent-validation-workflow.mdREADME.mdai-pic-frontend/package.json
Command Matrix
- Always run the minimum frontend gate:
cd ai-pic-frontend && npm run lint - Add tests when the change touches hooks, state logic, utilities, API client code, component behavior, or existing test files:
cd ai-pic-frontend && npm run test - Add a build for route, layout, config, auth, hydration, bundling, or SSR-sensitive changes:
cd ai-pic-frontend && npm run build
Decision Rules
- Treat
npm run lintas non-optional for frontend changes. - Add
npm run testwhenever the change modifies behavior rather than only copy, docs, or passive styling. - Add
npm run buildwhen the change can affect routing, layouts, server/client boundaries, config, auth redirects, or hydration. npm run buildis a risk-driven frontend gate. It does not replace the repository-wide./docker/build_prod_images.shrequirement before commit.- If the change is user-visible or login-related, pair this skill with
ai-video-studio-mcp-e2e.
Reporting Requirements
- Report the exact frontend commands that were run and why they were sufficient.
- When tests or build were omitted, state the risk assessment explicitly.
- In
agent_chats, put frontend evidence under## Validationbefore or alongside browser validation notes. - Do not collapse lint, tests, build, and browser checks into a vague sentence like "frontend verified".
Explicit Invocation
Use this skill explicitly from the repo path:
Use $ai-video-studio-frontend-test at /Users/geyunfei/dev/yfge/ai-video-studio/.codex/skills/ai-video-studio-frontend-test
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.
- 11d ago First seen · 54 lines · 83 tokens per session scan A 269b86c9072b
ai-video-studio-frontend-test is a skill published in the GitHub repository yfge/ai-video-studio (62 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 558 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
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.
quality-engineering-selector-stability
Cross-stack selector and test-id policy for web and mobile automation. Use when writing or reviewing E2E/UI test locators, or adding data-testid/accessibility identifiers to components.