band-play: Instructions file for Claude Code

CLAUDE.md

band-play CLAUDE.md is an instructions file for Claude Code from borbiuk/band-play. It costs 707 tokens per session, scanned A, original, MIT.

Repository instructions for Bandcamp Play, a Chrome browser extension for Bandcamp. They guide Claude Code through the project’s structure, rules, commands, and extension-specific constraints.

In plain words
What is it for?
Use them when changing Bandcamp Play, especially its Manifest V3 browser-extension code, message handling, documentation, or build process.
Why use it?
They reduce accidental changes and help the agent follow the project’s existing conventions. They also document safety limits for Git and Chrome extension work.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

This is borbiuk/band-play's own configuration. It tells Claude Code how to work on band-play itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything band-play configures →

Reuse

Borrowing it

Nothing to install: this file belongs to borbiuk/band-play. 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/borbiuk/band-play/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/borbiuk/band-play

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.

agentmods badge for band-play CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/borbiuk/band-play/claude-md/github.svg)](https://agentmods.dev/instructions/borbiuk/band-play/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/borbiuk/band-play/claude-md"><img src="https://agentmods.dev/badge/instructions/borbiuk/band-play/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.

agentmods 80×15 button for band-play CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/borbiuk/band-play/claude-md"><img src="https://agentmods.dev/badge/instructions/borbiuk/band-play/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 707 This file is loaded in full into every session.
When invoked 707 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00707 $0.00707
Opus 5.5 $0.00283 $0.00283
Sonnet 5.5 $0.00141 $0.00141
Haiku 4.5 $0.00071 $0.00071

Measured yesterday against content hash 28618dab9a16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

band-play 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 yesterday.

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 · 24 lines

How it starts

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

Claude Code — Band Play

@AGENTS.md

Working rules

  • Follow existing project conventions (code style, folder structure, naming, dependency management) unless explicitly instructed otherwise.
  • Never refactor unless explicitly requested; apply only the changes directly required for the current request. Keep changes minimal, explicit, and localized.
  • Always use a block if-return statement (avoid inline one-liners).
  • All comments and documentation must be in English; answer in the same language as the question.
  • Dependencies: only exact versions, never ^ or ~. Install with npm install -E <package>@latest, then run npm run check:versions.
  • Do not add attribution lines ("generated by", co-author trailers) to code, docs, release notes, commit messages or pull requests. .claude/settings.json turns off Claude Code's own commit and PR attribution.
  • Git safety: never run commit, reset, rebase, push, pull --force, checkout --force, clean, or stash drop unless the user explicitly asks; confirm before git pull, git merge, or git stash. The riskiest commands are also blocked or gated in .claude/settings.json.

Agent context

  • Rules (.claude/rules/) load automatically when matching files are touched: architecture, messaging (messages and ports), Bandcamp DOM selectors and page services, batch download, popup, Firefox, npm versions, docs and CI, testing, agent context.
  • Skill /verify (.claude/skills/verify/): exact versions, format, both builds, ESLint with the type check, web-ext lint, unit and e2e tests, the docs check and the unused code check.
  • Skill /release (.claude/skills/release/, invoked by the user only): version bump, release notes, release commit and zips, then after confirmation push, CI, tag and GitHub Release. The store upload is manual.
  • Skills for tests: /playwright (.claude/skills/playwright/: writing, running and debugging the Playwright suite, Chrome extension specifics) and /e2e-review (.claude/skills/e2e-review/: the test standard and the review workflow). Tests follow testing.md.
  • Subagents (.claude/agents/): code-reviewer (read-only review), qa-engineer (read-only verification), e2e-reviewer (read-only review of tests with /e2e-review), plus the generated Playwright agents playwright-test-planner, -generator and -healer (regenerate with npx playwright init-agents --loop=claude --project=e2e after a Playwright update; their output must pass /e2e-review).
  • Plugin modern-web-guidance (enabled in .claude/settings.json) provides the official chrome-extensions skill for Chrome APIs.
  • MCP servers (.mcp.json): chrome-devtools loads the unpacked build into Chrome for in-browser checks; playwright-test serves the Playwright test agents. init-agents overwrites .mcp.json, so re-add chrome-devtools after running it.

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

  1. yesterday Changed · +321 tokens per session 28618dab9a16
  2. 1mo ago First seen · 24 lines · 386 tokens per session scan A d63f11d5b68d

Subscribe to this mod's changes

band-play CLAUDE.md is an instructions file published in the GitHub repository borbiuk/band-play (21 stars, last pushed today), licensed MIT. It adds 707 tokens to every session, about $0.0028 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens