Use when adding, removing, or renaming an MCP tool in the bv-mcp / blackveil-dns repo — anything that touches TOOLDEFS in src/schemas/tool-definitions.ts or changes the tool count. Symptoms: 'Missing required parameter: domain' on a new tool, toHaveLength(N) spec failures, a category-count or score-snapshot assertion…
Use when operating bv-mcp's infrastructure surfaces — wrangler bindings (what a BV service binding does, which are operator-deploy-only, fail-soft semantics), deploy paths and workflow history (deploy-prod.yml, publish.yml, removed workflows), CI/CD workflow inventory and branch protection, the scandomain subrequest…
Use when bumping the version or cutting a release of the bv-mcp / blackveil-dns repo — version-sync across SERVERVERSION, package.json, package-lock.json, server.json, CHANGELOG, and the publish.yml tag flow. Symptoms: version mismatch CI failures, the publish workflow's auto-bump push rejected by branch protection…
Use when changing the bv-mcp / blackveil-dns scoring model — category weights, profiles, grade thresholds, the passed/missing-control rule, or the score computation in packages/dns-checks/src/scoring. Also use when computing an adoption, coverage, or zero-rate statistic from category scores across a corpus of domains.…
Use when writing or debugging tests in the bv-mcp / blackveil-dns repo — Vitest in the Cloudflare Workers pool, DNS mocking via dns-mock, dynamic-import mock isolation, cache clearing between cases, and the pyramid-layer filename suffixes. Symptoms: a mock leaking between tests, a tool not picking up mocked DNS, cache…
★not rated 9 todayA181 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: