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/realzachi/shotluma/agents-mdgit clone --depth 1 https://github.com/realZachi/shotlumaWrote 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.
[](https://agentmods.dev/instructions/realzachi/shotluma/agents-md)<a href="https://agentmods.dev/instructions/realzachi/shotluma/agents-md"><img src="https://agentmods.dev/badge/instructions/realzachi/shotluma/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00605 | $0.00605 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
shotluma 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 5d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shotluma agent instructions
Shotluma is a React 19, TypeScript, and Vite editor. Treat maintainability, user data, export accuracy, and secret handling as product behavior.
Required workflow
- Read this file and the linked rule documents relevant to the change.
- Inspect nearby code, tests, and
git statusbefore editing. Preserve unrelated user changes. - Keep the change focused. Refactor an affected boundary first if the requested work would otherwise deepen a violation.
- Add or update tests and documentation with the implementation.
- Run
bun run checkbefore handing off. Do not hide failures with disabled rules or weaker thresholds.
Use Bun for all package and script operations. Never use npm or manually edit bun.lock.
Commands
bun install— install the locked dependencies.bun run dev— start the editor athttp://127.0.0.1:4173.bun run typecheck— run strict TypeScript checks.bun run lint— run typed ESLint, architecture, and complexity rules.bun run test/bun run test:coverage— run the Vitest suite.bun run build— type-check and build the production bundle.bun run check— run every required local and CI quality gate.
Non-negotiable rules
- Keep editor mutations immutable; undo/redo snapshots depend on it.
- This public repository owns only the editor. The production marketing site is maintained privately and deployed separately; never add its source, styles, assets, or production-only configuration here.
- Never commit secrets, private screenshots, unlicensed assets, PSD/PSB files, or generated
dist/. - AI provider keys are entered in the browser (stored in
localStorage) with optional.env.localVITE_*fallback for local dev; Moonshot and OpenCode use a same-origin CORS proxy. Never commit.env.localor deploy a keyed build. - Use shadcn/Base UI and Hugeicons for editor chrome. Do not add a parallel UI or token system.
- Update generated
src/components/ui/files only with the shadcn CLI. - Use Conventional Commit messages and keep commits independently coherent.
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.
- 5d ago First seen · 45 lines · 605 tokens per session scan A cf40c1773ab8
shotluma AGENTS.md is an instructions file published in the GitHub repository realZachi/shotluma (115 stars, last pushed today), licensed MIT. It adds 605 tokens to every session, about $0.0030 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
claude-code-apple-skills CLAUDE.md
Claude Code instructions for rshankras/claude-code-apple-skills, covering claude.md, repository purpose, architecture, skill structure and yaml frontmatter (required).
storeshots-mcp AGENTS.md
Instructions for mtbun/storeshots-mcp, covering agents.md, what this project is, architecture, non-negotiable principles and layout contract (compose).
app-store-operator CLAUDE.md
Instructions for meyusufdemirci/app-store-operator, covering app store operator — mcp server, codebase, server wiring, tool module contract and prompts.
appshot AGENTS.md
Instructions for trunghaiy/appshot, covering agents.md, repository overview, architecture, repository structure and agent skills specification.
appshot CLAUDE.md
Instructions for trunghaiy/appshot, covering appshot — claude code project brief, key constraint, where things live, build and git.
claude-aso-audit-skill CLAUDE.md
Instructions for FelixGraeber/claude-aso-audit-skill, covering claude aso — app store optimization skill pack, architecture, commands, development rules and key principles.