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/ericrisco/rsc-harness/bronpx skills add ericrisco/rsc-harness --skill brogit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/bro)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/bro"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/bro.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.00076 | $0.01099 |
| Opus 5 | $0.00038 | $0.00549 |
| Sonnet 5 | $0.00015 | $0.00220 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
bro 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bro — say it like a person
Make the words sound like someone with something real to say. Keep the substance; remove the performance around it.
The contract
- Find the source without ceremony. A bare “bro”, “write like a human”, “hazlo más natural”, or equivalent points to the assistant's last answer. If the user pasted text, rewrite that. If they requested new copy, draft it directly. Ask for text only when no source exists.
- Preserve the payload. Keep names, facts, numbers, links, commitments, constraints, uncertainty and necessary warnings. Do not improve the prose by inventing evidence, opinions, anecdotes or certainty.
- Match the room. Keep the user's language and fit the audience, relationship and channel. A natural legal notice is still precise; a natural Slack message can be loose. “Human” does not automatically mean casual.
- Cut the bot-shaped scaffolding. Remove throat-clearing, needless summaries, repeated conclusions, corporate filler, fake enthusiasm, abstract nouns and headings or bullets that do not help the reader navigate.
- Restore a real cadence. Prefer concrete verbs, direct sentences and natural contractions. Vary sentence length when it helps. Use the words a person in this context would actually choose, without manufacturing slang, typos or choppy fragments.
- Return the writing, not a review of the writing. By default, output the rewritten or newly drafted text with no “here is a more human version” preface. Explain the changes only if asked.
When the original contains code, commands, URLs, quoted terms or regulated wording, leave those pieces exact unless the user explicitly asks to change them. Explain unavoidable jargon once in plain language instead of deleting precision.
What “human” means here
| Aim | The result |
|---|---|
| Plain, not simplistic | Easy to follow without losing the idea |
| Concise, not incomplete | No padding; all load-bearing facts remain |
| Warm, not performative | Appropriate care without canned empathy |
| Conversational, not sloppy | Natural rhythm without fake mistakes |
| Specific, not decorated | Concrete nouns and verbs instead of hype |
What ships with it
2 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.
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.
- 5d ago First seen · 77 lines · 76 tokens per session scan A ab93cd4b0270
bro is a skill published in the GitHub repository ericrisco/rsc-harness (64 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 1,099 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-08-30.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.