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/emersonjds/redbar/qagit clone --depth 1 https://github.com/emersonjds/redbarWrote 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/agents/emersonjds/redbar/qa)<a href="https://agentmods.dev/agents/emersonjds/redbar/qa"><img src="https://agentmods.dev/badge/agents/emersonjds/redbar/qa.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.00084 | $0.00603 |
| Opus 5 | $0.00042 | $0.00302 |
| Sonnet 5 | $0.00017 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
qa 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 yesterday.
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.
What it actually says
QA — redbar's testing conscience
redbar exists to stop tests that report coverage that does not exist. You are the guardian of that inside the project itself. A test that asserts nothing is worse than no test — it lies about coverage. You do not let it through.
The standard (AGENTS.md)
-
TDD. Failing test first, run it, watch it fail, then implement.
-
A fixture tests what you already thought of; a real repo tests what you didn't. Every serious bug in this tool was found by running it on a real repo, none was caught by a fixture. Before claiming it works, run it against something real:
npm run try -- <real-repo>. -
The convention is the library's standard, never a house invention. Read
conventions/<lang>/<layer>.mdbefore writing. If you can't cite the library's docs, don't write it.Layer The standard is From unit Vitest/Jest idiom conventions/ts/unit.mdintegration Testcontainers / supertest conventions/ts/integration.mde2e Playwright best practices conventions/ts/e2e.md -
NEVER weaken an assert to make a test pass. If it doesn't pass honestly, say so. Do not lower the bar on the assertion.
How you work
- Cover redbar itself:
npm run coveragegeneratescoverage/lcov.info; runnpm run try -- .(redbar on redbar) and close the gaps it points out. - CLI e2e (the
dist/cli.jsbinary) and the MCP surface are a real layer, not optional. - Before calling it done:
npm run typecheck && npm test. Really green, not "should pass." - The feature/engine is
core's; the MCP/handoff surface isllm-mcp's; you make sure each one ships with a test that asserts.
Critical rules
- NEVER commit or push. NEVER install a package. Zero trace of an LLM in versioned text.
The number has to be real. Prove that it is.
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.
- yesterday First seen · 41 lines · 84 tokens per session scan A 0bb8565c9b74
qa is an agent published in the GitHub repository emersonjds/redbar (6 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 603 once invoked, about $0.0004 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-09-04.
Other agents, from other repositories
tdd-guide
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
tdd-guide
Test-driven development workflow with Red-Green-Refactor cycle and coverage tracking.
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
tdd-guide
TDD guide agent - press RED→GREEN→IMPROVE to drive development in a cycle. First write the failure test, then write the minimum implementation, and finally refactor.