What is unflick CLAUDE.md?

Repository instructions for unflick, a desktop video player for Windows and macOS with a graphical app, command-line interface, and MCP server. They require new features to work through the command line and MCP before the graphical interface.

Use them when adding video-player features, implementing Rust core logic, exposing commands or MCP tools, and self-testing those features before building GUI support.

They give development priorities that keep the core usable and testable without opening the desktop interface.

How zhitongblog/unflick configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to zhitongblog/unflick. 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/zhitongblog/unflick/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/zhitongblog/unflick

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/zhitongblog/unflick/claude-md/github.svg)](https://agentmods.dev/instructions/zhitongblog/unflick/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/zhitongblog/unflick/claude-md"><img src="https://agentmods.dev/badge/instructions/zhitongblog/unflick/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/zhitongblog/unflick/claude-md"><img src="https://agentmods.dev/badge/instructions/zhitongblog/unflick/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,982 This file is loaded in full into every session.

When invoked 4,982 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.

Model	Per session	Once invoked
Fable 5.1	$0.04982	$0.04982
Opus 5	$0.02491	$0.02491
Sonnet 5	$0.00996	$0.00996
Haiku 4.5	$0.00498	$0.00498

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

Security

Grade A, and why

unflick 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 10d 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 · 455 lines

How it starts

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

unflick

A modern, beautiful, AI-ready video player for Windows and macOS.

Project Overview

unflick is a cross-platform video player that provides three interfaces:

GUI — Modern UI for regular users (React + TypeScript + Tailwind)
CLI — Command-line control for power users and scripts
MCP Server — AI agent integration via Model Context Protocol

All three interfaces share a unified Rust core.

Core Constraint: CLI/MCP First

Every feature MUST be fully functional via CLI and MCP before it is considered complete.

This is non-negotiable. The development loop is:

Build the Rust core logic
Expose it via CLI command + MCP tool
Self-test through CLI/MCP (Claude can verify its own work)
Only then build the GUI layer on top

A feature without CLI/MCP coverage does NOT ship. The first usable release (v0.1) must be 100% operable through CLI and MCP — GUI is a bonus, not a requirement for v0.1.

Why

Claude can self-test every feature during development via CLI and MCP
Ensures the Rust core is clean and decoupled from any UI
CLI/MCP users get first-class support, not an afterthought
Forces good architecture: if it works headless, the GUI is just a skin

Self-Test Protocol

After implementing any feature, Claude MUST verify it by:

Running the CLI command and checking stdout/exit code
Calling the MCP tool and validating the JSON response
If either fails, fix before moving on — do NOT defer to "test later"
Adding a case to src-tauri/tests/ — a verification that lives only in a chat transcript is gone the moment the session ends

Test suite

pnpm test                  # frontend unit tests (vitest, no DOM needed)

cd src-tauri
cargo test                 # everything: unit + integration
cargo test --lib           # unit only (fast, no media needed)
cargo test --test playback -- --test-threads=2

Frontend tests cover the pure logic that has no business being verified by hand: chord derivation in lib/keys.ts (which must agree byte-for-byte with core::keybind::normalize, or a binding stores fine and never fires) and the gesture/wheel thresholds in lib/gesture.ts. They deliberately avoid a DOM environment — the functions read plain fields, so a test can pass a plain object.

Read the full file on GitHub · 455 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.

10d ago First seen · 455 lines · 4,982 tokens per session scan A d9efa89a9380

Subscribe to this mod's changes

unflick CLAUDE.md is an instructions file published in the GitHub repository zhitongblog/unflick (0 stars, last pushed today), licensed MIT. It adds 4,982 tokens to every session, about $0.0249 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.

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

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

unflick: Instructions file for Claude Code