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 skills/qball-inc/the-bulwark/component-patternsnpx skills add QBall-Inc/the-bulwark --skill component-patternsgit clone --depth 1 https://github.com/QBall-Inc/the-bulwarkWrote 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/skills/qball-inc/the-bulwark/component-patterns)<a href="https://agentmods.dev/skills/qball-inc/the-bulwark/component-patterns"><img src="https://agentmods.dev/badge/skills/qball-inc/the-bulwark/component-patterns.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.1 | $0.00020 | $0.01189 |
| Opus 5 | $0.00010 | $0.00594 |
| Sonnet 5 | $0.00004 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
component-patterns scanned grade A 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `expect(fetch).toHaveBeenCalledWith(url)` | `const resp = await fetch(url); expect(resp.status).toBe(200)` | Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| Imports `child_process`, has `spawn`/`exec`/`execSync` | Process Spawner | `references/pattern-process-spawner.md` | Copies of this mod
1 near-identical copy found in the catalogue:
- component-patterns — 89% identical, 267 lines differ
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Patterns
Purpose
Provide verification strategies for different component types. This skill defines how to test real behavior for CLIs, servers, parsers, processes, databases, and external APIs.
When to Use
Load this skill when:
- Generating verification scripts via bulwark-verify skill
- Determining how to test a specific component type
- Implementing test-audit Step 7 rewrites
Component Type Detection
Analyze the code to determine component type based on these indicators:
| Indicators | Component Type | Pattern Reference |
|---|---|---|
Imports child_process, has spawn/exec/execSync |
Process Spawner | references/pattern-process-spawner.md |
Imports http/https/express/fastify/koa, has listen() |
HTTP Server | references/pattern-http-server.md |
Imports fs, reads/parses files, has parse functions |
File Parser | references/pattern-file-parser.md |
Has CLI argument parsing (process.argv, yargs, commander, argparse) |
CLI Command | references/pattern-cli-command.md |
Imports database driver (pg, mysql, mongoose, sqlite, prisma) |
Database | references/pattern-database.md |
Makes outbound HTTP calls (fetch, axios, got, requests) |
External API | references/pattern-external-api.md |
Pattern Reference Files
Each pattern reference contains:
- Strategy: High-level approach for testing the component type
- Templates: Ready-to-use verification script templates in Bash, Node/Jest, and Python/pytest
- Placeholders: Variables to substitute with component-specific values
Available Patterns
| Pattern | File | Languages |
|---|---|---|
| CLI Command | references/pattern-cli-command.md |
Bash, Node, Python |
| HTTP Server | references/pattern-http-server.md |
Bash, Node (supertest), Python |
| File Parser | references/pattern-file-parser.md |
Bash, Node, Python |
| Process Spawner | references/pattern-process-spawner.md |
Bash, Node |
| Database | references/pattern-database.md |
Node, Python, Bash (SQLite) |
| External API | references/pattern-external-api.md |
Node (MSW), Python (responses) |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 137 lines · 20 tokens per session scan A 121f8a622d22
component-patterns is a skill published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,189 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ros2-microros
Skill "ros2-microros" from Leehyunbin0131/claude-ros2-skills, covering micro-ros instructions (ubuntu 24.04 lts & ros 2 jazzy), 1. architecture, 2. documentation entry points, 3. key concepts & patterns and a. embedded client node setup (rclc in c).
ros2-troubleshooting
Diagnose ROS 2 Jazzy faults that reading the code cannot settle: QoS mismatch, sensor-mount and frame errors (REP 103/105), and odometry calibrated against CAD instead of the floor. Ships four runnable pass/fail checks.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.