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 skills add kochetkov-ma/claude-brewcode --skill e2egit clone --depth 1 https://github.com/kochetkov-ma/claude-brewcodeWrote 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/kochetkov-ma/claude-brewcode/e2e)<a href="https://agentmods.dev/skills/kochetkov-ma/claude-brewcode/e2e"><img src="https://agentmods.dev/badge/skills/kochetkov-ma/claude-brewcode/e2e/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/skills/kochetkov-ma/claude-brewcode/e2e"><img src="https://agentmods.dev/badge/skills/kochetkov-ma/claude-brewcode/e2e.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.00037 | $0.01768 |
| Opus 5.5 | $0.00015 | $0.00707 |
| Sonnet 5.5 | $0.00007 | $0.00354 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
e2e 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing
Full-cycle E2E testing orchestration: install agents, create BDD scenarios, write autotests, quorum review.
Prompt contract
$ARGUMENTS is one free-form RU/EN prompt; mode tokens and flags may sit anywhere in it.
| Mode | EN keywords | RU keywords | Mutates? |
|---|---|---|---|
status |
(empty), status, check, show |
статус, проверь, покажи |
no |
install |
install, setup, set up, init |
настрой, установи, поставь |
yes |
create |
create, write, add tests, new scenario |
создай, напиши, добавь тесты |
yes |
update |
update, refresh, sync tests |
обнови, актуализируй |
yes |
review |
review, quorum, validate |
ревью, провалидируй |
yes |
rules |
rules, conventions, e2e rules |
правила, конвенции |
yes |
- Mode: an explicit mode token wins outright; else the most distinct whole-word keyword hits
(table above). Tie with a destructive mode ->
AskUserQuestion; withstatus->status; of two mutating modes -> the keyword that comes first. No hit or empty ->statusif the e2e agent roster is installed (.claude/agents/e2e-*.mdcount >= 3), elseinstall. - Scope: prose that is not a mode/id/path is still input: take the id, path or target from it.
- Ask: at most ONE
AskUserQuestion(max 4 questions) to resolve mode and scope, before any work, only when the answer changes what gets written. A read-only run asks nothing.
Print once, before the first action (labels literal, values in the conversation language):
PLAN — brewcode:e2e
INPUT: <arguments verbatim, or "(empty)">
MODE: <resolved> — <explicit | matched keyword: X | default>
SCOPE: <resolved paths / target / level / flags>
DO: <2-5 imperative bullets>
RESULT: <what the user ends up holding>
Phase 0: Parse Arguments
What ships with it
12 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.
- LICENSE 1.1 KB
- README.md 1.6 KB
- references/agent-template.md 2.8 KB
- references/e2e-architecture.md 9.3 KB
- references/e2e-rules.md 5.7 KB
- references/mode-create.md 11 KB
- references/mode-install.md 10 KB
- references/mode-review.md 5.2 KB
- references/mode-rules.md 8.0 KB
- references/mode-status.md 4.0 KB
- references/mode-update.md 6.1 KB
- scripts/detect-mode.sh 6.2 KB runs code
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 Changed · +1 lines b5d210a5a3ba
- 2d ago Changed 29a0152e0e60
- 3d ago Changed 5f67b3dbbf93
- 4d ago Changed 2fd1640b1f31
- 5d ago Changed · -64 lines c0a5fae36079
- 12d ago Changed 3c590c7d5d43
- 17d ago Changed · -1 lines 14d18ff34f48
- 1mo ago Changed 1aa164451025
- 1mo ago First seen · 222 lines · 37 tokens per session scan A 907b3faca770
e2e is a skill published in the GitHub repository kochetkov-ma/claude-brewcode (37 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,768 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-08-30.
Other skills, from other repositories
demo-review
Quality-checks a rendered demo video before it ships — extracts frames, grades each section against its successCriteria, and finds spinners, empty states, clipped text, exposed secrets, audio/video desync, and pacing problems. Use after a draft render, before a final render, or when asked whether a demo video is good…
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
cypress-ops
Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…
playwright-ops
Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".