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 amajorai/ryu --skill brogit clone --depth 1 https://github.com/amajorai/ryuWrote 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/amajorai/ryu/bro)<a href="https://agentmods.dev/skills/amajorai/ryu/bro"><img src="https://agentmods.dev/badge/skills/amajorai/ryu/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/amajorai/ryu/bro"><img src="https://agentmods.dev/badge/skills/amajorai/ryu/bro.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.00016 | $0.00060 |
| Opus 5.5 | $0.00006 | $0.00024 |
| Sonnet 5.5 | $0.00003 | $0.00012 |
| Haiku 4.5 | $0.00002 | $0.00006 |
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 8 lines · 16 tokens per session scan A aa329d0ceeee
bro is a skill published in the GitHub repository amajorai/ryu (41 stars, last pushed yesterday), with no licence file. It adds 16 tokens to every session and 60 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-09-12.
Other skills, from other repositories
explainshell
Explain shell commands in plain English (explainshell.com).
jw-apologetics
Answer doctrinal questions with verified citations from jw.org. Use when the user asks "¿qué dice la Biblia / Watch Tower sobre X?", "¿qué creemos sobre Y?", "respóndele a este argumento", or any topic that touches on JW doctrine (Trinity, soul, last days, blood, holidays, etc.).
jw-meeting-prep
Prepare comments and study material for the weekly Watchtower Study or midweek meeting. Use when the user asks for "preparar la Atalaya", "preparar la reunión", "comentarios para la reunión", "estudio de esta semana", or shares a wol.jw.org article URL and asks for meeting prep.
jw-research
Multi-step research on jw.org content — search publications, fetch articles, cross-reference verses, summarize with verified citations. Use when the user asks an open-ended doctrinal or topical question that needs more than one verse lookup.
jw-verse-lookup
Resolve a Bible reference in any language to its canonical wol.jw.org URL with structured book/chapter/verse data. Use whenever the user mentions a verse like "Juan 3:16", "Heb 13", or "1 Corinthians 13:4-7".
jw-daily-text
Fetch today's daily text (texto diario) from wol.jw.org. Use when the user asks for "el texto diario", "today's text", "texto de hoy", or to share/explain today's scripture and commentary.