Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/syi0808/screenize/agents-mdgit clone --depth 1 https://github.com/syi0808/screenizeWhat 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 | $0.01239 | $0.01239 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
screenize 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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for autonomous coding agents working in this repository.
Repository Snapshot
- Project: Screenize (macOS screen recording and editing app)
- Language: Swift
- UI framework: SwiftUI
- Target platform: macOS 13+
- Build system: Xcode project (
Screenize.xcodeproj) - External dependency: Sparkle (via Swift Package Manager)
Mandatory Agent Workflow
Follow this sequence for each meaningful work unit:
- START: run the
work-context-finderagent to check prior related work. - WORK: implement the task.
- FINISH: execute
/log-workusing thework-loggerskill.
Notes:
- This workflow is defined in
CLAUDE.mdand should be treated as repository policy. - All generated logs/summaries/tags for vector DB workflows must be in English.
Build, Lint, and Test Commands
Run all commands from repository root (/Users/sung-yein/Workspace/screenize).
Build
xcodebuild -project Screenize.xcodeproj -scheme Screenize -configuration Debug build
Lint
./scripts/lint.sh
Auto-fix lint violations where possible:
./scripts/lint.sh --fix
Tests (Current Status + How To Run)
Current repository status:
- There is currently no test target configured in
Screenize.xcodeproj. - There are currently no
*Tests*files/directories in the repo. - Primary verification today is successful build + lint.
When tests are added, use these command patterns:
Run all tests for a scheme:
xcodebuild -project Screenize.xcodeproj -scheme Screenize -destination 'platform=macOS' test
Run a single test class:
xcodebuild -project Screenize.xcodeproj -scheme Screenize -destination 'platform=macOS' -only-testing:ScreenizeTests/MyFeatureTests test
Run a single test method:
xcodebuild -project Screenize.xcodeproj -scheme Screenize -destination 'platform=macOS' -only-testing:ScreenizeTests/MyFeatureTests/testExample test
Tip: if scheme/target names differ, inspect with:
xcodebuild -list -project Screenize.xcodeproj
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.
- 2d ago First seen · 146 lines · 1,239 tokens per session scan A 587e76e9792d
screenize AGENTS.md is an instructions file published in the GitHub repository syi0808/screenize (601 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,239 tokens to every session, about $0.0062 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-30.
Other instructions, from other repositories
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.