sanzaru: Instructions file for Codex

AGENTS.md

sanzaru AGENTS.md is an instructions file for Codex, OpenCode from TJC-LP/sanzaru. It costs 722 tokens per session, scanned A, original, MIT.

Contributor instructions for the Sanzaru Python project, an MCP server that connects coding agents to media-generation tools. MCP is a standard way for an AI agent to call tools provided by another program.

In plain words
What is it for?
Use them to set up Sanzaru, run its server, connect it to Codex, generate or download media, check job status, manage references, and follow the project's coding conventions.
Why use it?
They explain how to install, run, connect to, and smoke-test the server, avoiding setup mistakes. They also document the available video, image, and reference-image operations.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

This is TJC-LP/sanzaru's own configuration. It tells Codex and OpenCode how to work on sanzaru itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sanzaru configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TJC-LP/sanzaru. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TJC-LP/sanzaru/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/TJC-LP/sanzaru

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for sanzaru AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tjc-lp/sanzaru/agents-md.svg)](https://agentmods.dev/instructions/tjc-lp/sanzaru/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/tjc-lp/sanzaru/agents-md"><img src="https://agentmods.dev/badge/instructions/tjc-lp/sanzaru/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 722 This file is loaded in full into every session.
When invoked 722 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00722 $0.00722
Opus 5 $0.00361 $0.00361
Sonnet 5 $0.00144 $0.00144
Haiku 4.5 $0.00072 $0.00072

Measured 8d ago against content hash 15657eb92b5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

sanzaru 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 8d 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.

AGENTS.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

This document helps contributors work effectively in this repository.

Project Structure & Module Organization

  • src/sanzaru/ — MCP server (entrypoint server.py, CLI sanzaru).
  • videos/, images/ — Downloaded videos and reference images (git-ignored).
  • README.md — Setup and tool usage; setup.sh — interactive setup; .mcp.json — sample MCP config.

Build, Test, and Development Commands

  • Install deps: uv sync (use uv venv first if needed).
  • Run server: uv run sanzaru (loads .env).
  • Quick start: ./setup.sh (prompts for OPENAI_API_KEY, creates folders, installs deps).
  • Codex integration (from repo root):
    • codex mcp add sanzaru -- uv run --directory "$(pwd)" sanzaru
  • Smoke test (via MCP tools): create a video/image, poll status, then download (see README for tool list).

Sora Toolkit & Prompting

  • Tools: create_video, get_video_status, download_video, list_videos, delete_video, remix_video; images: create_image, get_image_status, download_image; refs: list_videos_references, prepare_reference_image.
  • Flows: Video only (create → poll → download) or Image → Video (generate image → download → use as input_reference_filename).
  • Prompting: see docs/sora2-prompting-guide.md. Think “action + subject + scene + style + camera + lighting + mood”.
  • Example: create_video(prompt="wide tracking shot of a neon-lit rainy alley, cinematic, 35mm", size="1280x720", seconds="8")

Coding Style & Naming Conventions

  • Python 3.10+, typed (prefer TypedDict, explicit return types).
  • snake_case for functions/vars, PascalCase for classes, constants UPPER_SNAKE.
  • Lint/format with ruff (line length 120, py310). Run: uv run ruff check . and uv run ruff format ..

Testing Guidelines

  • No formal tests yet. Do manual smoke tests: create → status → download for videos/images.
  • Verify files land in videos/ and images/; include exact steps in PRs.

Commit & Pull Request Guidelines

  • Commits: imperative mood, concise scope first (e.g., feat: add create_image tool).
  • Group related changes; avoid drive-by refactors.
  • PRs: include purpose, screenshots/paths of created files, and testing steps (commands + observed output).
  • Link issues when applicable; note any follow-ups.

Read the full file on GitHub · 45 lines

Changes

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.

  1. 8d ago First seen · 45 lines · 722 tokens per session scan A 15657eb92b5e

Subscribe to this mod's changes

sanzaru AGENTS.md is an instructions file published in the GitHub repository TJC-LP/sanzaru (6 stars, last pushed 24d ago), licensed MIT. It adds 722 tokens to every session, about $0.0036 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens