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.
git clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/commands/axiomantic/spellbook/test-bar-remove)<a href="https://agentmods.dev/commands/axiomantic/spellbook/test-bar-remove"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/test-bar-remove/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.
<a href="https://agentmods.dev/commands/axiomantic/spellbook/test-bar-remove"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/test-bar-remove.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01742 |
| Opus 5.5 | $0.00010 | $0.00697 |
| Sonnet 5.5 | $0.00005 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
test-bar-remove 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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MISSION
Completely remove all test apparatus code injected by /test-bar. Restore every modified file to its pre-injection state. Delete every created file. Verify the working tree is clean relative to the branch's actual feature changes.
Invariant Principles
- Safety before speed - Check for user modifications before reverting. Never destroy work the developer added on top of the test bar injection.
- Manifest is source of truth - The manifest tells you exactly what was created and modified. Trust it over heuristics.
- Verify after removal - Confirm the project compiles and no broken imports remain. A partial removal is worse than no removal.
- Graceful fallback - If the manifest is missing, attempt heuristic detection. Report clearly and exit if detection fails.
Step 1: Read Manifest
cat $SPELLBOOK_CONFIG_DIR/test-bar-manifest.json 2>/dev/null
If manifest exists: Parse it and proceed to Step 2.
If manifest does NOT exist: Fall back to heuristic detection:
# Search for test bar artifacts
echo "=== COMPONENT FILES ==="
find src/ -name "TestScenarioBar*" -o -name "testScenarioData*" 2>/dev/null
echo "=== INJECTION POINTS ==="
grep -rn "TestScenarioBar\|test-scenario-bar\|Test Scenario Bar" src/ \
--include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" 2>/dev/null
echo "=== DEV-ONLY COMMENTS ==="
grep -rn "DEV-ONLY: Test scenario bar\|remove with /test-bar-remove" src/ \
--include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" 2>/dev/null
- If artifacts found: Build a synthetic manifest from the search results and proceed with user confirmation.
- If nothing found: Report "No test bar found to remove. No manifest at
$SPELLBOOK_CONFIG_DIR/test-bar-manifest.jsonand no TestScenarioBar artifacts detected in source." and exit.
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.
- 1mo ago First seen · 217 lines · 26 tokens per session scan A 4d499119d1a5
test-bar-remove is a command published in the GitHub repository axiomantic/spellbook (11 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,742 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
test-browser
Run browser tests on pages affected by current PR or branch.
test-suite
Run comprehensive test suite with coverage analysis.
test-integration.en
Run the integration test workflow.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
zeus
A command that runs an automated software-building pipeline from a one-line product description through planning, implementation, review, Docker setup, and testing.