Borrowing it
Nothing to install: this file belongs to khajaaijaz26/agent-demo-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/khajaaijaz26/agent-demo-studio/main/AGENTS.mdgit clone --depth 1 https://github.com/khajaaijaz26/agent-demo-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/instructions/khajaaijaz26/agent-demo-studio/agents-md)<a href="https://agentmods.dev/instructions/khajaaijaz26/agent-demo-studio/agents-md"><img src="https://agentmods.dev/badge/instructions/khajaaijaz26/agent-demo-studio/agents-md/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/instructions/khajaaijaz26/agent-demo-studio/agents-md"><img src="https://agentmods.dev/badge/instructions/khajaaijaz26/agent-demo-studio/agents-md.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.00590 | $0.00590 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
agent-demo-studio AGENTS.md 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 9d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Video-production rules for AI agents
These rules apply when Codex, Claude Code, or another agent uses this repository or its MCP server to create a video.
Never create blindly
Before recording, generating audio, assembling a timeline, or rendering, inspect
the selected production stack with demo_capabilities, agent-demo capabilities,
or inspectCapabilities(). Then create a production plan from the user's request
with demo_creator_plan, agent-demo creator plan, or the equivalent library
function. The plan must cover:
- The goal, intended audience, duration, output formats, narration, and source strategy.
- Visual style, pacing, composition, characters, animation, transitions, and VFX.
- A timed, scene-by-scene storyboard whose visuals match the active narration or sensory beat.
- A complete resource list identifying supplied, bundled, generated, optional, and missing media plus its provenance and rights status.
- The step-by-step production workflow, assumptions, and quality gates.
Persist the plan as production-plan.json. demo_creator_from_prompt and
agent-demo creator prompt do this automatically before media generation. They
also attach the request-aware capability report to the plan and stop after saving
it when a selected required tool is unavailable.
Build from the plan
- Resolve required resources before the scene that needs them.
- Do not substitute a network or paid provider for a missing local capability. Report the blocker and its setup instruction from the saved plan.
- Treat bundled characters and scenes as optional starters, never a fixed cast. Accept any authorized uploaded or locally generated characters and scene media required by the brief, and record their provenance.
- Build the editable manifest scene by scene; do not discard plan requirements.
- Keep narration at a natural pace and adjust scene duration instead of speeding speech unnaturally.
- Keep captions, titles, characters, lower thirds, and CTAs in separate readable regions and within each export's safe zones.
- Inspect representative frames and transitions for overlap, clipping, black bands, mismatched narration, and disclosure issues before declaring completion.
- Use a voice clone only through a loopback local adapter and only when the plan records the authorized speaker's name, confirmed consent, and intended scope.
- Prefer the smallest suitable local Qwen model for speed, make at most one planning inference per video, and preserve the deterministic fallback and fixed production rules.
- Return the plan, manifest, videos, captions, thumbnails, chapters, and rights report as local artifact paths.
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.
- 9d ago First seen · 55 lines · 590 tokens per session scan A 8cd7fa8aaaf6
agent-demo-studio AGENTS.md is an instructions file published in the GitHub repository khajaaijaz26/agent-demo-studio (1 stars, last pushed 8d ago), licensed MIT. It adds 590 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.