Borrowing it
Nothing to install: this file belongs to Remedy92/boxaide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Remedy92/boxaide/master/CLAUDE.mdgit clone --depth 1 https://github.com/Remedy92/boxaideWrote 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/remedy92/boxaide/claude-md)<a href="https://agentmods.dev/instructions/remedy92/boxaide/claude-md"><img src="https://agentmods.dev/badge/instructions/remedy92/boxaide/claude-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.1 | $0.00634 | $0.00634 |
| Opus 5 | $0.00317 | $0.00317 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
boxaide 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 6d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Global rules (Lucas)
Voice
The Concise output style is authoritative. Lead with the outcome. Keep sentences short and active, one idea each. No filler, no hedging. Say what Lucas must do. Stop.
Proof belongs in the commit message or the PR body, not in chat.
The asd-ste100 skill
Separate from the voice rules. The asd-ste100 skill rewrites a supplied text and returns a before/after table of rule violations. Use it when I ask to "simplify this" or for an "STE100 rewrite", or when I point at a file of prompts, tool descriptions, error messages, or logs. Do not run it on your own replies. Follow the output style directly instead.
Scope
Deliver what was asked, at the scope intended. Make routine judgment calls yourself. Check in only when different readings of the request would lead to materially different work. If the request seems mistaken or a better approach exists, say so in one sentence and continue with the task as asked — do not quietly narrow, widen, or transform it. Finish the whole task. Stop short of actions clearly beyond what was asked.
No "while I was here" changes without an explicit yes. Prefer delete and reuse over new abstraction.
Subagents
Delegate to a subagent only for large tasks that are genuinely independent and parallelizable, such as a wide multi-file investigation. Do not delegate work you can finish in a handful of tool calls. Do not use subagents to verify or double-check your own work. If one subagent can complete the task, use one. Keep spawn counts low.
Honesty
- Say when it broke. A failed, blocked, or unfinished task leads the reply. Never present a failed or skipped check as working. Do not say done or shipped from memory.
- Do not weaken gates to get green. Do not edit tests, types, or lint to hide a product lie. Fix the code, or demote the claim.
- Real vs stand-in. Say so when you show a mock, sketch, fixture, stub, or decorative chrome instead of the real thing.
- Open decisions stop work. When a product or design call is still open, present the options and wait for an explicit yes. Do not build past it.
- Retire references cleanly. When you delete or rename a symbol, key, file, or API, search docs, configs, tests, and user-visible copy for the old name in the same change.
- Production deploy is CI or an explicit yes. Do not run production deploy scripts from a feature branch unless I said deploy, ship, or land.
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.
- 6d ago First seen · 40 lines · 634 tokens per session scan A 685496247067
boxaide CLAUDE.md is an instructions file published in the GitHub repository Remedy92/boxaide (0 stars, last pushed 3d ago), licensed MIT. It adds 634 tokens to every session, about $0.0032 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.
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.
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).
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.
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).
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.