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.5 | $0.00033 | $0.00223 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (68 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 558 once invoked, about $0.0003 per session on Opus 5.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
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.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
oma-refactor
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
oma-qa
Review changes for correctness, security, accessibility, and performance. Use for scoped quality reviews or verification plans; bug fixes use oma-debug.
oma-debug
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.