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 principle-laziness-protocolgit 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/principle-laziness-protocol)<a href="https://agentmods.dev/skills/amajorai/ryu/principle-laziness-protocol"><img src="https://agentmods.dev/badge/skills/amajorai/ryu/principle-laziness-protocol/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/principle-laziness-protocol"><img src="https://agentmods.dev/badge/skills/amajorai/ryu/principle-laziness-protocol.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.00042 | $0.00295 |
| Opus 5.5 | $0.00017 | $0.00118 |
| Sonnet 5.5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
principle-laziness-protocol 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 · 19 lines · 42 tokens per session scan A 9006579e9e3f
principle-laziness-protocol is a skill published in the GitHub repository amajorai/ryu (41 stars, last pushed yesterday), with no licence file. It adds 42 tokens to every session and 295 once invoked, about $0.0002 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
cflx-workflow
Legacy compatibility router for Conflux apply, rejecting, cleanup-review, accept, and archive operations. New orchestrator prompts use dedicated cflx- operation skills. CRITICAL - This skill CANNOT ask questions or request user input.
simplify-code
Parallel 4-agent cleanup of recent code changes.
dws
A command-line guide for DingTalk, a workplace platform with chat, documents, calendars, approvals, tasks, and other business tools.
tmeet-skill
A command-line tool for Tencent Meeting, a video-conferencing service. It covers sign-in, meetings, recordings, transcripts, reports, invitations, and controls during a meeting.
community-research-insight
Extract structured insight briefs from community research transcripts or notes. Produces pain points, stakeholder needs, opportunity maps, risks, and follow-up questions. Requires human review before publication.
output-eval-error-analysis
Systematically review workflow traces to identify failure modes before building evaluators. Use when starting an eval project, after significant pipeline changes, or when production quality drops.