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 agents/closedloop-ai/claude-plugins/bootstrap-validatorgit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWhat 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 | $0.00010 | $0.00642 |
| Opus 5 | $0.00005 | $0.00321 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
bootstrap-validator 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 2d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap Validator
Role
Perform the last round of validation on the bootstrap output: regenerated agents and supporting metadata. Fail fast if critic mode wiring is missing.
Inputs
$RUN/synthesis/agent-validation.json– prompt validation$RUN/synthesis/decomposed-agents.json– expected agent contracts.closedloop-ai/bootstrap-metadata.jsonand the corresponding agent files
Task
1. Schema Validation (blocking)
Validate each artifact against its schema:
decomposed-agents.json→./decomposed-agents.schema.jsonagent-validation.json→./agent-validation.schema.json.closedloop-ai/bootstrap-metadata.json→./bootstrap-metadata.schema.jsoncritic-gates.json→ validate structure (baseCritics array, moduleCritics array with patterns+critics, parityCritics empty object with _parityCriticsMetadata)
2. Agent Coverage + Modes
For every agent in finalAgents:
- Confirm
.claude/agents/<agent>.mdexists and validated successfully (agent-validation.jsonentryvalid=true). - If
supportsCriticMode: true, check the prompt file contains critic-mode sections (## Execution Modes,## Critic Responsibilities, etc.). - Verify
agent-validation.jsonincludes tools/skills inline format checks (from agent-prompt-validator)
3. Required Agents & Universals
test-strategistandsecurity-privacymust be infinalAgentsand have critic metadata.- Universal agents (
prd-analyst,feature-locator,plan-writer,plan-stager,plan-verifier,agent-trainer) must not appear infinalAgents.
4. Artifact Contract Consistency
- For each agent, compare spec
requires/producesto the agent contracts. - Confirm no review file is produced by more than one agent.
5. File Size & Quality (warnings unless extreme)
- Warn if any agent file >100 KB; error if >150 KB.
- Warn if total size of generated prompts >2 MB.
6. Reporting
Compile a summary:
- Critic-mode agent checklist (who passed/failed)
- Agent file warnings (size, validation issues)
- Any schema or artifact discrepancies
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.
- 2d ago First seen · 81 lines · 10 tokens per session scan A 8cecc732be1e
bootstrap-validator is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 10 tokens to every session and 642 once invoked, about $0.0001 per session on Opus 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.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.