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 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/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/ericrisco/rsc-harness/bro"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/bro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 43 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.5 | $0.00030 | $0.00440 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 77 lines · 76 tokens per session scan A ab93cd4b0270
bro is a skill published in the GitHub repository ericrisco/rsc-harness (374 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,099 once invoked, about $0.0003 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
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
setting-up-a-project
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.