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/emersonjds/redbar/redbar.initnpx skills add emersonjds/redbar --skill redbar.initgit 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/skills/emersonjds/redbar/redbar.init)<a href="https://agentmods.dev/skills/emersonjds/redbar/redbar.init"><img src="https://agentmods.dev/badge/skills/emersonjds/redbar/redbar.init.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.00096 | $0.00607 |
| Opus 5 | $0.00048 | $0.00303 |
| Sonnet 5 | $0.00019 | $0.00121 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade A, and why
redbar.init 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Optional. A repo path.
The one rule
Never install a dependency. Never edit package.json, pom.xml, Cargo.toml, composer.json, or any other manifest.
Not "ask first, then install". Not "install if it seems safe". Print the command and stop. Editing someone's manifest unasked is a rejected PR at best and a supply-chain incident at worst. The human presses enter, or does not.
This holds even if the human seems to want you to move fast. Print the command.
Outline
-
Run init from the project root:
npx redbar init $ARGUMENTSFall back to
npx tsx src/cli.ts init $ARGUMENTSifredbaris not on PATH. -
Report what it proposes, exactly:
- which language and runner it detected (and how — which manifest file gave it away)
- which test libraries are missing, grouped by layer (unit / integration / e2e)
- the exact install command, verbatim, in a copyable block
- the coverage command to run afterwards
-
Stop there. Do not run the install. Do not run the coverage command either — it can be slow, and it is the human's call.
-
If the human explicitly says "go ahead, install it", you may run the install command exactly as printed — no extra packages, no version bumps, no "while I'm here" additions.
What to say about the libraries
The libraries redbar proposes are the standard ones for that ecosystem, not exotic picks. If the human asks why a given library:
- The unit libs are the runner the project already uses, plus its coverage reporter — redbar needs the coverage report to exist at all.
- The integration libs are the ones the library's own docs point at (Testcontainers for Spring, httpx for Python, supertest for Node).
- The e2e lib is Playwright, in every ecosystem that has a binding.
If the project already has a different but equivalent library, say so and leave it alone. The goal is a coverage report redbar can read, not a specific dependency list.
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 · 53 lines · 96 tokens per session scan A c317c0449fcd
redbar.init is a skill published in the GitHub repository emersonjds/redbar (6 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 607 once invoked, about $0.0005 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 skills, from other repositories
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
test-commander
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration). Covers Vitest/Jest, Testing Library, Playwright, MSW for API mocking, snapshot strategy, visual regression (Chromatic/Percy/Playwright), test factories with Faker, and CI sharding. Use when user…
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.
testing-strategy
Choose the right test type for every change — unit, integration, contract, end-to-end, property-based, mutation, fuzz. Use when adding tests to a new feature, deciding what to test for a bug fix, designing a test pyramid for a service, evaluating coverage targets, or untangling a slow test suite. Stack-agnostic…
test-sweep
Run all test suites (unit, integration, API, E2E) and aggregate results into a summary report. Use after completing execution slices or before the Review Gate.