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.
git clone --depth 1 https://github.com/mryll/skillsWrote 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/plugins/mryll/skills/mryll-skills)<a href="https://agentmods.dev/plugins/mryll/skills/mryll-skills"><img src="https://agentmods.dev/badge/plugins/mryll/skills/mryll-skills/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/plugins/mryll/skills/mryll-skills"><img src="https://agentmods.dev/badge/plugins/mryll/skills/mryll-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mryll-skills 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 3d 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.
What it actually says
{
"name": "mryll-skills",
"source": "./",
"description": "Mryll's collection of research-backed Claude Code skills",
"version": "1.15.0",
"strict": false,
"skills": [
"./skills/agentmd",
"./skills/low-complexity",
"./skills/vertical-slice-architecture",
"./skills/codex-review",
"./skills/codex-discuss",
"./skills/test-namer",
"./skills/dual-testing",
"./skills/explain-pr",
"./skills/como-si-fuera-de-boca",
"./skills/pr-quiz",
"./skills/study-session",
"./skills/ste",
"./skills/c4-model",
"./skills/claude-review",
"./skills/claude-discuss",
"./skills/agent-context-auditor",
"./skills/practitioner-voice-review"
]
}What it installs
The manifest is a name and a version. 17 skills travel with it, and installing the plugin installs all of them — 2,993 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill c4-model A 180 tokens
- Skill ste A 127 tokens
- Skill low-complexity A 153 tokens
- Skill test-namer A 116 tokens
- Skill vertical-slice-architecture A 150 tokens
- Skill agent-context-auditor A 237 tokens
- Skill practitioner-voice-review A 176 tokens
- Skill dual-testing A 208 tokens
- Skill study-session A 117 tokens
- Skill como-si-fuera-de-boca A 235 tokens
- Skill pr-quiz A 129 tokens
- Skill explain-pr C 197 tokens
- Skill agentmd C 175 tokens
- Skill codex-discuss D 196 tokens
- Skill codex-review D 198 tokens
- Skill claude-discuss D 199 tokens
- Skill claude-review D 200 tokens
What ships with it
1 file beside marketplace.json#mryll-skills 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.
- 3d ago Changed · +1 lines 333bbc397170
- 1mo ago First seen · 25 lines scan A aff581a8745a
mryll-skills is a plugin published in the GitHub repository mryll/skills (6 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
mattpocock-skills
A collection of coding-agent skills for practical software engineering, including test-driven development, code review, debugging, design, and specification work.
animal-geneticist-breeder
Reasons from additive genetic variance, response to selection (R = i h sigmaA), accuracy, and inbreeding depression through REML/BLUP and ssGBLUP pipelines (BLUPF90, ASReml, WOMBAT), economic selection indices, optimum-contribution mate allocation, and Interbull MACE while treating confounded contemporary groups, pred.
animal-scientist
Reasons from NRC nutrient requirements, ad libitum intake, energy/protein partitioning, and genotype x environment x management through ration software (CNCPS, NDS, NRC), pen-blocked trials with mixed models (lme4, PROC MIXED), and BCS, NIR, and rumen/BHBA diagnostics while treating intake collapse, milk fat…
actuarial-scientist
Reasons from mortality tables (qx, period/cohort, select/ultimate) and Chain-Ladder/Mack reserving through GLM/GAM frequency–severity and Tweedie pricing, limited-fluctuation and Bühlhmann-Straub credibility, Solvency II SCR standard formula, and IFRS 17 CSM/RA while treating triangle truncation, overfitting, and tail.
aerospace-engineer
Reasons from margin-managed factors of safety, mass properties, and the analysis-test-similarity V&V hierarchy through FUN3D/SU2 CFD, NASTRAN/Abaqus FEA, JSBSim/Simulink 6-DOF, and FAR/CS, DO-178C, and NASA-STD compliance while treating flutter, buckling, inlet distortion, mass growth, and single-point failures as…
agricultural-engineer
Reasons from mass, energy, and momentum balances on variable biological media through ET-based scheduling, psychrometric grain-drying balances, ASABE D497 draft estimates, EPANET pipe networks, and RTK-GNSS/ISOBUS precision-ag validation while treating soil compaction, clogged drip emitters, grain-bin hotspots, GPS…