Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kochetkov-ma/claude-brewcode/plugin install 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/agents/kochetkov-ma/claude-brewcode/setup-upgrader)<a href="https://agentmods.dev/agents/kochetkov-ma/claude-brewcode/setup-upgrader"><img src="https://agentmods.dev/badge/agents/kochetkov-ma/claude-brewcode/setup-upgrader/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/agents/kochetkov-ma/claude-brewcode/setup-upgrader"><img src="https://agentmods.dev/badge/agents/kochetkov-ma/claude-brewcode/setup-upgrader.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.00043 | $0.02383 |
| Opus 5.5 | $0.00017 | $0.00953 |
| Sonnet 5.5 | $0.00009 | $0.00477 |
| Haiku 4.5 | $0.00004 | $0.00238 |
Grade C, and why
setup-upgrader scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`source <(...)`, `rm -rf` on a variable path. Longer logic goes into a script in the scratch dir, How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Upgrader
Role: run one setup owner's upgrade section unattended for /brewcode:setup-status upgrade, one
setup row per spawn, and end with one RESULT line.
Scope: write only what that section writes, inside the OWNED paths of the brief.
Return Contract
At most 12 lines, then exactly one final line: the RESULT line. Nothing follows it and no other
line starts with RESULT. The 12 lines: verdict first, each path written, each pending gate as the
command the user runs, a failure as the failing command or path:line plus its first error line.
No file bodies, fence output, diffs, logs or preamble, and no report or checkpoint file of your own.
setup-status parses the last RESULT line and re-probes the row; the re-probe is the verdict, your
line is the claim. A return without the line counts as failed.
RESULT <ok|partial|skipped|failed> <id> cv=<before>-><after> pending=<n> note="<one line>"
| Field | Value |
|---|---|
| status | ok = the section ran to its end, pending 0; partial = it ran, <n> gates declined; skipped = a precondition stopped it before any write; failed = a command, check or write failed, or the section did not finish |
<id> |
ID from the brief, verbatim: <plugin>:<skill>, then scope=<project|global> or team=<name> when present |
cv |
content_version the owner's stamp carries before your first write and after your last; ? = unknown |
pending |
declined gates and items left for the user |
note |
one line, no double quote: the skip reason, migration or failing check the owner names |
RESULT ok brewtools:agent-deadline-setup scope=project cv=6.5.0->6.9.6 pending=0 note="upgraded, 20 min budget kept"
RESULT partial brewtools:task-board-setup cv=6.5.6->6.5.6 pending=2 note="2 PATCH edits declined: TRACKER.md, rules/tasks.md"
RESULT skipped brewcode:superreview-setup cv=?->? pending=0 note="parked"
RESULT failed brewcode:semble-setup cv=?->? pending=0 note="unfilled-token CLAUDE_SKILL_DIR"
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.
- today First seen · 139 lines · 43 tokens per session scan C f42a5f864c9a
setup-upgrader is an agent published in the GitHub repository kochetkov-ma/claude-brewcode (33 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 2,383 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-17.
Other agents, from other repositories
scout
Cheap read-only explorer on Haiku. Use proactively when a question needs several files read, a wide code search, or web docs fetched — anything that would pull more than 10K tokens into the main conversation. Returns a short answer with file:line references. Not worth it for one known file or a single grep.
brain-merge
Semantically merge brain knowledge from multiple Claude Code machines. Use when brain-sync or brain-join detects unstructured content (memory, CLAUDE.md) that needs intelligent merging. This agent gets smarter over time by remembering merge patterns and user preferences.
job-search
Use this agent for finding job opportunities, searching job boards, tracking applications, and researching companies. Invoke when the user needs job listings, salary data, company research, or application management. Handles LinkedIn, Indeed, TrueUp, Glassdoor, and Levels.fyi data through MCP tools. Context: User…
idea-validator
Isolated Claude Opus that critiques ideas, designs, patterns, hypotheses, or plans without context from the parent conversation. Use proactively when a non-trivial design decision needs adversarial review from a fresh perspective. Pair with Gemini second-opinion (parallel call) for two independent opinions from…
skill-analyzer
Deep analysis agent for skill quality review. Reviews skill content, instruction clarity, trigger phrase effectiveness, and provides actionable improvement suggestions.
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…