Borrowing it
Nothing to install: this file belongs to sausi-7/carousels. 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/sausi-7/carousels/main/AGENTS.mdgit clone --depth 1 https://github.com/sausi-7/carouselsWrote 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/sausi-7/carousels/agents-md)<a href="https://agentmods.dev/instructions/sausi-7/carousels/agents-md"><img src="https://agentmods.dev/badge/instructions/sausi-7/carousels/agents-md.svg" alt="Measured on agentmods" 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.01432 | $0.01432 |
| Opus 5 | $0.00716 | $0.00716 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
carousels 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 6d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
carousels — agent instructions
Read this if you are a coding agent asked to make an Instagram carousel.
You are driving a design system, not writing one. The compositions, palettes, typography and motion already exist and are enforced by a validation gate. Your job is the content and the choices: the story arc, the copy, the theme, and the three per-slide levers. Do not write CSS, invent colours, or hardcode a font size — the gate will reject it and it would be worse anyway.
One-time setup
<repo>/skills/carousels/bin/carousels setup
Installs Remotion and a headless Chromium. A few hundred megabytes, a few minutes, once per machine. Tell the user before you start it. Every other command refuses to run until this has happened.
Requires Node 20+. ffmpeg is optional (Remotion bundles its own; only the
contact-sheet step uses a system one).
Commands
All output lands in ./carousels/<runId>/ relative to the directory you run
from. Use the absolute path to the wrapper.
CAROUSELS=<repo>/skills/carousels/bin/carousels
"$CAROUSELS" suggest --text "<the brief>" # rank the ten themes
"$CAROUSELS" check <runId> # validate; --strict to block on warnings
"$CAROUSELS" render <runId> # produce the files
"$CAROUSELS" preview --matrix # design stills, no video
"$CAROUSELS" gallery # contact sheet of rendered runs
"$CAROUSELS" test # self-test the design system
The pipeline
Work in this order. Each step writes a file.
-
Brief →
carousels/<runId>/brief.json. Ask only what you cannot infer: topic, goal, audience, tone, slide count (6–8 default, 4–10 allowed), what the CTA asks for, brand colours or a wordmark.Also ask the output format, unless the request settles it:
formatOutput Cost video(default)one silent MP4 per slide + a thumbnail ~25s for six slides stillsone lossless PNG per slide ~4s for six slides bothboth as video
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.
- 6d ago First seen · 135 lines · 1,432 tokens per session scan A a7df5fc3e3e1
carousels AGENTS.md is an instructions file published in the GitHub repository sausi-7/carousels (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,432 tokens to every session, about $0.0072 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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.