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/judell/bram/claude-mdgit clone --depth 1 https://github.com/judell/bramWrote 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/judell/bram/claude-md)<a href="https://agentmods.dev/instructions/judell/bram/claude-md"><img src="https://agentmods.dev/badge/instructions/judell/bram/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 | $0.02552 | $0.02552 |
| Opus 5 | $0.01276 | $0.01276 |
| Sonnet 5 | $0.00510 | $0.00510 |
| Haiku 4.5 | $0.00255 | $0.00255 |
Grade A, and why
bram 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 4d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bram
You are running in the terminal of a Tauri desktop shell. The shell puts a real terminal (where you run) next to an agent pane the user can SEE while talking to you. It can optionally also show a right-pane target-app iframe, but that pane is off by default and often absent — most users run their app in their own browser. Detect before you assume an iframe is there; when one is present, use it.
Keep two distinct surfaces straight — they are not the same, and the rules differ:
- The agent pane — Bram's own UI (the Worklist / Transcript / Sessions /
Context / Status tabs). Always XMLUI — that's how Bram
is built. Editing it means
app/tools/Main.xmlui,app/tools/components/*.xmlui,app/__shell/helpers.js,app/tools/Globals.xs. - The target app — whatever project the user is developing with Bram's
help, shown in the optional target-app iframe when that pane is
enabled (off by default, often absent). Per
app/__shell/conventions.md, Bram "works with any project that serves a web UI (vanilla HTML/JS, a React or other Node app, a Python web app, an XMLUI app, etc.)." It may or may not be XMLUI — detect before you assume, and don't assume the pane is even present.
The XMLUI-specific guidance below is unconditional when working on Bram itself, and applies to the target app only when the target is XMLUI.
Working on Bram itself (the agent pane is XMLUI)
Most edits to Bram land in .xmlui files. Rules the xmlui-standalone
evaluator enforces hard:
- No raw browser JS in event handlers —
setTimeout,setInterval,fetchoutside DataSource,async/await, etc. are rejected at evaluation time with an unhandled rejection. Stay within App abstractions:delay(ms),debounce(ms, fn, ...args), theTimercomponent,DataSourcefor HTTP,ChangeListenerfor derived reactivity. - Lead with the xmlui-mcp tools before reaching for a JS solution.
The
xmlui_search_howtotool is the fastest way to find the XMLUI-native pattern for a feature (e.g. "delay function", "debounce input", "wrap text in table cell");xmlui_component_docsis for component-prop lookups;xmlui_get_promptre-injects the server's framing guidance mid-session when you suspect you've drifted. - Cite a doc URL for any non-obvious markup decision —
https://www.xmlui.org/docs/reference/components/<Name>orhttps://www.xmlui.org/docs/howto/<slug>. If you can't cite one, search again.
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.
- 4d ago First seen · 207 lines · 2,552 tokens per session scan A 6c7bd0570d97
bram CLAUDE.md is an instructions file published in the GitHub repository judell/bram (46 stars, last pushed today), licensed Apache-2.0. It adds 2,552 tokens to every session, about $0.0128 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
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).
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.
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.