bulwark-verify

bulwark-verify is a skill for Claude Code from QBall-Inc/the-bulwark. It costs 28 tokens per session (3,927 once invoked), scanned C, original, MIT.

A tool that creates runnable scripts for checking whether a software component behaves correctly, without using mocks. A component can be a program part such as a command-line tool or server.

In plain words
What is it for?
Use it to generate verification scripts for a component, optionally run them, or support a test audit that needs executable checks.
Why use it?
It turns checks into executable verification instead of leaving them as suggestions or mock-based tests. This helps confirm real behavior.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the the-bulwark plugin — 30 skills, 17 agents, 6 hooks shipped together

Good fit Use it to generate verification scripts for a component, optionally run them, or support a test audit that needs executable checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/qball-inc/the-bulwark/bulwark-verify
Install

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.

Any agent
npx skills add QBall-Inc/the-bulwark --skill bulwark-verify
Clone the repo
git clone --depth 1 https://github.com/QBall-Inc/the-bulwark

Made for: Claude Code.

Or install the-bulwark, the plugin that ships this one along with the rest of its 30 skills, 17 agents, 6 hooks.

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 bulwark-verify

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/qball-inc/the-bulwark/bulwark-verify"><img src="https://agentmods.dev/badge/skills/qball-inc/the-bulwark/bulwark-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,927 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00028 $0.03927
Opus 5 $0.00014 $0.01963
Sonnet 5 $0.00006 $0.00785
Haiku 4.5 $0.00003 $0.00393

Measured 11d ago against content hash 22be6792c23d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade C, and why

bulwark-verify scanned grade C with 2 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 11d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Manual cleanup: `rm -rf tmp/verification/*`

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- Has `spawn`/`exec`/`execSync` imports → Process Spawner
skills/bulwark-verify/SKILL.md · 542 lines

How it starts

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

Bulwark Verify

Purpose

Generate runnable verification scripts that test real component behavior without mocks. This skill orchestrates assertion-patterns (P2.1) and component-patterns (P2.2) to produce executable scripts for any component type.

When to Use

Load this skill when:

  • User requests /bulwark-verify [path]
  • test-audit Step 7 needs verification scripts
  • Generating standalone verification for a component

DO NOT use for:

  • Running existing tests (use just test)
  • Writing unit tests (implement directly)
  • Test auditing (use test-audit skill)

Usage

/bulwark-verify [path] [--execute]

Examples:

  • /bulwark-verify src/cli.ts - Generate verification script for CLI
  • /bulwark-verify src/server.ts --execute - Generate and run
  • /bulwark-verify - Infer from recent context

MANDATORY EXECUTION STEPS

WARNING: These steps are BINDING instructions, not suggestions. You MUST execute each step in order. Do NOT substitute your judgment for these instructions. Do NOT skip sub-agent spawning. Do NOT modify the execution flow.

When this skill is loaded, execute these steps exactly as written:

Step 1: Resolve Target

IF $ARGUMENTS provided:
    target = first non-flag argument
    execute_flag = "--execute" in $ARGUMENTS
ELSE:
    Look for component files in recent conversation context
    IF found: target = that path
    ELSE: Ask user: "Which component should I generate a verification script for?"

Step 2: Detect Project Language

Check for project manifest files in order (search from target file's directory up to project root):

Check Language Test Runner
package.json exists Node jest/vitest/node
pyproject.toml OR setup.py exists Python pytest/python
Cargo.toml exists Rust cargo test
None of the above Generic bash

Step 3: Analyze Component

  1. Read the target file

  2. Identify component type using indicators from component-patterns skill:

    • Has spawn/exec/execSync imports → Process Spawner
    • Has listen()/createServer/express()/fastify() → HTTP Server
    • Has fs.readFile/parse functions → File Parser
    • Has process.argv/yargs/commander/argparse → CLI Command
    • Has database imports (pg, mysql, mongoose, prisma) → Database
    • Has fetch/axios/got/requests calls → External API

Read the full file on GitHub · 542 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. 11d ago First seen · 542 lines · 28 tokens per session scan C 22be6792c23d

Subscribe to this mod's changes

bulwark-verify is a skill published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 3,927 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

journey-simulation

Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…

RockyHong/super-bootstrap · 79 tokens

black-box-test

Use as an INDEPENDENT tester agent to test another agent's intesting ticket from the OUTSIDE — never your own, and never from the implementation diff. You test from the operational test contract + acceptance criteria only (never HOW it was built), writing automated tests that invoke the changed surfaces and recording…

tmj-90/gaffer · 122 tokens

java-conventions

Use when a ticket adds or changes Java code and it must follow the repo's Java conventions — modern Java (records, sealed types, pattern matching, switch expressions), Optional discipline, immutability, Spring Boot constructor injection, and JUnit 5 + Mockito tests. Invoke for "add this in Java", "fix the Java build"…

tmj-90/gaffer · 89 tokens

python-conventions

Use when a ticket adds or changes Python code and it must follow the repo's Python conventions — PEP 8, full type hints, dataclasses, pythonic idioms, explicit error handling, and pytest with coverage. Invoke for "add this in Python", "fix the type/lint errors", "add the FastAPI/Django endpoint", or as the language…

tmj-90/gaffer · 84 tokens

add-integration-test

Use when a ticket asks for integration or end-to-end coverage across components — an API route hitting a database, a service-to-service call, a multi-step flow — rather than a single unit. Invoke for "test the endpoint end to end", "cover the checkout flow", or "verify the migration + query together".

tmj-90/gaffer · 69 tokens

record-evidence

Use after implementing a Dispatch ticket and running its checks, to produce and record acceptance-criterion evidence, then STOP. Invoke whenever you have finished and committed work on your claimed ticket and need to evidence each AC. Recording evidence is where your job ENDS — the runner (not you) records the…

tmj-90/gaffer · 76 tokens