What is screenize CLAUDE.md?

Project instructions for screenize, a macOS screen-recording and editing app. They define coding principles, when to plan larger tasks, and how to use separate agents for focused work.

Use them when developing screenize or working on its codebase. They guide planning, subtask delegation, root-cause fixes, and updates to the project's lessons file.

They give coding agents a consistent workflow for making and checking changes. They also require recording lessons after user corrections.

How syi0808/screenize configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to syi0808/screenize. 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/syi0808/screenize/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/syi0808/screenize

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/syi0808/screenize/claude-md/github.svg)](https://agentmods.dev/instructions/syi0808/screenize/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/syi0808/screenize/claude-md"><img src="https://agentmods.dev/badge/instructions/syi0808/screenize/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/syi0808/screenize/claude-md"><img src="https://agentmods.dev/badge/instructions/syi0808/screenize/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,282 This file is loaded in full into every session.

When invoked 2,282 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.02282	$0.02282
Opus 5.5	$0.00913	$0.00913
Sonnet 5.5	$0.00456	$0.00456
Haiku 4.5	$0.00228	$0.00228

Measured 2mo ago against content hash 48440533efeb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

screenize 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 2mo 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 · 231 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Core Principles

Simplicity First: Make every change as simple as possible. Impact minimal code.
No Laziness: Find root causes. No temporary fixes. Senior developer standards.
Minimal Impact: Changes should only touch what's necessary. Avoid introducing bugs.

Workflow Orchestration

Plan Node Default

Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions).
If something goes sideways, STOP and re-plan immediately — don't keep pushing.
Use plan mode for verification steps, not just building.
Write detailed specs upfront to reduce ambiguity.

Subagent Strategy

Use subagents liberally to keep main context window clean.
Offload research, exploration, and parallel analysis to subagents.
For complex problems, throw more compute at it via subagents.
One task per subagent for focused execution.

Self-Improvement Loop

After ANY correction from the user: update tasks/lessons.md with the pattern.
Write rules for yourself that prevent the same mistake.
Ruthlessly iterate on these lessons until mistake rate drops.
Review lessons at session start for relevant project.

Verification Before Done

Never mark a task complete without proving it works.
Diff behavior between main and your changes when relevant.
Ask yourself: "Would a staff engineer approve this?"
Run build, check logs, demonstrate correctness.

Demand Elegance (Balanced)

For non-trivial changes: pause and ask "is there a more elegant way?"
If a fix feels hacky: "Knowing everything I know now, implement the elegant solution."
Skip this for simple, obvious fixes — don't over-engineer.
Challenge your own work before presenting it.

Autonomous Bug Fixing

When given a bug report: just fix it. Don't ask for hand-holding.
Point at logs, errors, failing tests — then resolve them.
Zero context switching required from the user.
Go fix failing CI tests without being told how.

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

2mo ago First seen · 231 lines · 2,282 tokens per session scan A 48440533efeb

Subscribe to this mod's changes

screenize CLAUDE.md is an instructions file published in the GitHub repository syi0808/screenize (619 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 2,282 tokens to every session, about $0.0091 per session on Opus 5.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-30.

screenize CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
screenize CLAUDE.mdsyi0808/screenize	Instructions file	619	5mo ago	Apache-2.0	A	2,282	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

screenize: Instructions file for Claude Code