agentmods.dev

band-play: Skill for Claude Code

.claude/skills/verify/SKILL.md

verify is a skill for Claude Code from borbiuk/band-play. It costs 77 tokens per session (1,054 once invoked), scanned A, original, MIT.

A project check routine that runs formatting, builds, linting, type checks, documentation checks, and unit and end-to-end tests. It stops at the first failure and reports the affected files.

In plain words
What is it for?
Use it after changing code, the browser-extension manifest, or dependencies, or when you need to verify the project before submitting changes.
Why use it?
It replaces a long list of manual checks with one consistent sequence, helping catch broken builds, style problems, unused code, and test failures after changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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 →

not rated 21repo today A scan 77 tokens original MIT
View source ↗ borbiuk/band-play chromewebstore.google.com
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/skills/verify/SKILL.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 verify

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/borbiuk/band-play/verify"><img src="https://agentmods.dev/badge/skills/borbiuk/band-play/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,054 The whole file, excluding the scripts and references it only reads on demand.
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.00077 $0.01054
Opus 5.5 $0.00031 $0.00422
Sonnet 5.5 $0.00015 $0.00211
Haiku 4.5 $0.00008 $0.00105

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

Security

Grade A, and why

verify 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/skills/verify/SKILL.md · 44 lines

How it starts

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

Run in order and stop at the first failing step:

  1. npm run check:versions (every version in package.json is exact)
  2. npm run format:check (Prettier --check, as in CI)
  3. npm run build (Chrome, dist/)
  4. npm run build:firefox (Firefox, dist-firefox/)
  5. npm run lint (ESLint on the whole repository, then the TypeScript 7 type check of src/ and of tests/ with tests/tsconfig.json)
  6. npm run lint:firefox (web-ext lint on dist-firefox/; see the expected warnings below)
  7. npm run test:unit (Playwright unit project: pure logic from src/, no browser)
  8. npm run test:e2e (Playwright e2e project: the dist setup project rebuilds dist/ first, then the extension runs in Playwright's bundled Chromium against Bandcamp snapshots, no network)
  9. npm run lint:docs (markdownlint with the Prettier style, then scripts/check-docs.mjs: relative links and the release headings)
  10. npm run lint:unused (knip with knip.jsonc: unused files, exports and dependencies)

Steps 1 to 7 are the order of the build job in build.yml, and step 8 is its e2e job. Steps 9 and 10 are its checks job.

Expected web-ext lint warnings

web-ext lint exits 0 with 0 errors, 0 notices and 16 warnings (measured on version 11.0.0). All 16 are expected:

Count Code File Why it is expected
1 KEY_FIREFOX_UNSUPPORTED_BY_MIN_VERSION manifest.json browser_specific_settings.gecko.data_collection_permissions needs Firefox 140, but strict_min_version is 128. AMO requires the key; older Firefox versions ignore it
1 KEY_FIREFOX_ANDROID_UNSUPPORTED_BY_MIN_VERSION manifest.json The same key needs Firefox for Android 142
8 UNSUPPORTED_API background.js Chrome-only APIs that the code feature-detects: downloads.setUiOptions, downloads.setShelfEnabled, downloads.onDeterminingFilename (batch download) and power.requestKeepAwake / power.releaseKeepAwake (Keep Awake)
6 UNSAFE_VAR_ASSIGNMENT (innerHTML) content.js, options.js, downloads.js (2 each) Bundled React DOM code; src/ has no innerHTML

Report any other warning, any change in these counts, and every error or notice as a finding. Print the full list with npx --no web-ext lint --source-dir dist-firefox --output json when the counts differ.

Read the full file on GitHub · 44 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 First seen · 44 lines · 77 tokens per session scan A 23e09a151347

Subscribe to this mod's changes

verify is a skill published in the GitHub repository borbiuk/band-play (21 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,054 once invoked, about $0.0003 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-10-26.

E2E testingReactTestingUnit testingbandcampchromechrome-extensionmusictailwind
Related

Other skills, from other repositories

verify-work

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

HoangNguyen0403/agent-skills-standard · 23 tokens

test-building-blocks

Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from…

bartstc/vite-ts-react-template · 0 tokens

extension-test

Set up and run unit, integration, and E2E tests for Chrome extensions. Covers Jest mocks for chrome. APIs and Puppeteer E2E with real Chrome.

quangpl/browser-extension-skills · 37 tokens

testing-best-practices

Support QA and testing work across formats: planning checks, writing test cases, reviewing coverage, designing Playwright browser and component integration tests, creating locators, and keeping automated tests focused on observable product behavior.

siberiacancode/agent-skills · 47 tokens

e2e-tester

Test a web app like a QA person — open it in a real browser, click through flows, and report what's broken with screenshots and code references. Works on localhost. Use when the user wants to test their app, verify a flow works, check for visual bugs, or validate changes before pushing.

hanzili/hanzi-browse · 66 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens