splicedeck: Instructions file for Claude Code

CLAUDE.md

splicedeck CLAUDE.md is an instructions file for Claude Code from ihuzaifashoukat/splicedeck. It costs 541 tokens per session, scanned A, original, Apache-2.0.

Project instructions for Claude Code when working on splicedeck, a local video editor driven by AI agents. They explain how to follow the repository contract, run tests, and update generated command interfaces.

In plain words
What is it for?
Use them when Claude Code changes the project, runs its tests, updates commands, or troubleshoots the local MCP server, a standard way for AI tools to call commands.
Why use it?
They help Claude Code avoid stale documentation, incorrect test assumptions, and direct edits to generated files. They also describe how to check whether the local command server is working.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code; mentions AGENTS.md.

This is ihuzaifashoukat/splicedeck's own configuration. It tells Claude Code how to work on splicedeck 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 splicedeck configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ihuzaifashoukat/splicedeck. 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/ihuzaifashoukat/splicedeck/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/ihuzaifashoukat/splicedeck

Made for: Claude Code.

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 splicedeck CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ihuzaifashoukat/splicedeck/claude-md.svg)](https://agentmods.dev/instructions/ihuzaifashoukat/splicedeck/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/ihuzaifashoukat/splicedeck/claude-md"><img src="https://agentmods.dev/badge/instructions/ihuzaifashoukat/splicedeck/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 541 This file is loaded in full into every session.
When invoked 541 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.00541 $0.00541
Opus 5 $0.00270 $0.00270
Sonnet 5 $0.00108 $0.00108
Haiku 4.5 $0.00054 $0.00054

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

Security

Grade A, and why

splicedeck CLAUDE.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 7d 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.

CLAUDE.md · 41 lines

What it actually says

@AGENTS.md

Claude Code

AGENTS.md above is the contract: twelve hard rules and the table that says which document owns which concern. It is imported, not summarised. A summary here would be a shortcut you could read instead of the source, and it would go stale first.

This file carries only what AGENTS.md does not.

Run the tests as python -m pytest. pyproject.toml sets testpaths, so the bare command finds everything. Do not copy a test path out of a document without checking it exists — several filenames cited in docs/ were never written.

Both surfaces are generated from splicedeck/surface/verbs.py. Edit that table, never terminal.py or mcp.py's tool list. After any surface change run python -m checks.golden --check, and regenerate with python -m checks.golden when the diff is intended. The golden files exist so a surface change is reviewable.

The MCP server is spd serve, or python -m splicedeck.surface.mcp. Both reach the same loop. --tools prints the generated tool list and exits, which is how you tell a broken server from a broken host config.

A fixture must not fabricate its input. This is the expensive lesson in this repository, not a style preference. A one-line stub named bookmarks/baseline.toml kept the suite green for months while draft — and therefore every verb downstream of it — could not run at all on a real clone. Media fixtures encoded -preset ultrafast, which disables B-frames, so no test ever saw the cadence misclassification that blocked every camera export. When a test needs shipped data, read the shipped data.

Git has no commits yet. A 223 MB .mov sits at the repository root; it is covered by .gitignore, and git check-ignore is how you confirm that rather than assuming it. Do not stage or commit anything unless asked.

Where the open questions are. docs/roadmap.md Open items and the Open sections of each owner document are genuinely undecided. AGENTS.md says not to resolve one silently, and the ones most likely to tempt you are the twelve selectable bookmarks (docs/bookmarks.md B-2) and the axes they are points in (B-1). Inventing them would fix public names by accident.

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. 7d ago First seen · 41 lines · 541 tokens per session scan A 8635ca3e361b

Subscribe to this mod's changes

splicedeck CLAUDE.md is an instructions file published in the GitHub repository ihuzaifashoukat/splicedeck (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 541 tokens to every session, about $0.0027 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,182 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