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-backend-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-backend-test)<a href="https://agentmods.dev/skills/yfge/ai-video-studio/ai-video-studio-backend-test"><img src="https://agentmods.dev/badge/skills/yfge/ai-video-studio/ai-video-studio-backend-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-backend-test"><img src="https://agentmods.dev/badge/skills/yfge/ai-video-studio/ai-video-studio-backend-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.00100 | $0.00682 |
| Opus 5 | $0.00050 | $0.00341 |
| Sonnet 5 | $0.00020 | $0.00136 |
| Haiku 4.5 | $0.00010 | $0.00068 |
Grade A, and why
ai-video-studio-backend-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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Video Studio Backend Test
Use this skill to choose the smallest backend validation set that still matches the risk of the change. Reuse the repo's existing commands; do not invent new wrapper scripts or treat run_pytest.py as the default contract.
Read First
AGENTS.mddocs/testing/agent-validation-workflow.mdai-pic-backend/TESTING_GUIDE.mdai-pic-backend/pytest.iniai-pic-backend/tests/README.md
Command Matrix
- Quick regression for narrow service, validator, prompt, or repository changes:
cd ai-pic-backend && python run_tests.py quick - Full backend gate for migrations, auth, API shape changes, task orchestration, or pre-commit confidence:
cd ai-pic-backend && pytest - Targeted validation when touched code has a clear nearby test surface:
cd ai-pic-backend && pytest <path-or-node> -v - Diagnostic or marker-driven helper flows only when the task explicitly needs them:
cd ai-pic-backend && python run_pytest.py --diagnostic cd ai-pic-backend && python run_pytest.py --external
Decision Rules
- Start with targeted
pytest <path-or-node>only when the change is isolated and the relevant tests are obvious. - Escalate to
python run_tests.py quickwhen the change affects shared utilities, serialization, prompts, or multiple backend modules. - Escalate to full
pytestfor migrations, repository/model changes, auth, API contracts, background tasks, or whenever earlier checks fail. - If the task mentions provider integrations or env-gated tests, read the markers in
ai-pic-backend/pytest.inibefore choosing a path. - Treat
run_pytest.pyas an auxiliary helper for diagnostic or external-marker flows. Do not present it as the main backend entrypoint.
Reporting Requirements
- Report the exact backend command that was run and the high-signal result.
- In
agent_chats, record backend evidence under## Validationwith command, scope, and outcome. - If a lighter validation path was chosen, explain why it matched the risk.
- If a backend change affects login, UI-visible behavior, or AI/media generation, pair this skill with
ai-video-studio-mcp-e2e.
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 · 60 lines · 100 tokens per session scan A b07d1275d0f7
ai-video-studio-backend-test is a skill published in the GitHub repository yfge/ai-video-studio (62 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 682 once invoked, about $0.0005 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
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.
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
channel-bot
Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.
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.
python-backend
Production Python async patterns including asyncio TaskGroup, FastAPI dependency injection and middleware, SQLAlchemy 2.0 async sessions, and database connection pool tuning. Python 3.11+ runtime concerns such as ExceptionGroup, cancellation semantics, and session rollback. Use when building async services, wiring…
testing-integration
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.