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/code-yeongyu/lazyclaudecodeWrote 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/code-yeongyu/lazyclaudecode/omo)<a href="https://agentmods.dev/plugins/code-yeongyu/lazyclaudecode/omo"><img src="https://agentmods.dev/badge/plugins/code-yeongyu/lazyclaudecode/omo/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/code-yeongyu/lazyclaudecode/omo"><img src="https://agentmods.dev/badge/plugins/code-yeongyu/lazyclaudecode/omo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
omo 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.
What it actually says
{
"name": "omo",
"version": "0.1.0",
"description": "One Claude Code plugin namespace for Yeongyu's local Claude Code components.",
"author": {
"name": "Yeongyu Kim",
"email": "[email protected]",
"url": "https://github.com/code-yeongyu"
},
"homepage": "https://github.com/code-yeongyu/lazyclaudecode",
"repository": "https://github.com/code-yeongyu/lazyclaudecode",
"license": "MIT",
"keywords": ["claude-code", "claude-code-plugin", "omo", "hooks", "mcp", "skills"],
"skills": "./skills/",
"hooks": "./hooks/hooks.json",
"mcpServers": "./.mcp.json",
"interface": {
"displayName": "OMO",
"shortDescription": "Unified local Claude Code components",
"longDescription": "OMO exposes the local Claude Code Rules, Comment Checker, LSP, Ultrawork, and Ultragoal components as one plugin namespace while keeping each component isolated under components/ for maintenance.",
"developerName": "Yeongyu Kim",
"category": "Developer Tools",
"capabilities": ["Hooks", "MCP Tools", "Code Intelligence", "Workflow", "Context Injection"],
"websiteURL": "https://github.com/code-yeongyu/lazyclaudecode",
"privacyPolicyURL": "https://github.com/code-yeongyu/lazyclaudecode#privacy",
"termsOfServiceURL": "https://github.com/code-yeongyu/lazyclaudecode#license",
"defaultPrompt": [
"Use OMO LSP diagnostics on this workspace.",
"Show which OMO rules matched this file.",
"ulw: run this change with evidence."
],
"brandColor": "#D97757",
"screenshots": []
}
}
What it installs
The manifest is a name and a version. 14 skills, 6 agents, 1 hook, 2 MCP servers travel with it, and installing the plugin installs all of them — 1,484 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill programming A 261 tokens
- Skill remove-ai-slops A 182 tokens
- Skill review-work A 116 tokens
- Skill planing-prometheustic A 104 tokens
- Skill init-deep A 14 tokens
- Skill start-work A 63 tokens
- Skill ai-slop-remover A 32 tokens
- Skill frontend-ui-ux A 21 tokens
- Skill ulw-loop C 24 tokens
- Skill refactor A 29 tokens
- Skill lsp A 27 tokens
- Skill debugging A 244 tokens
- Skill rules A 28 tokens
- Skill comment-checker A 29 tokens
- Agent librarian A 64 tokens
- Agent planner A 60 tokens
- Agent metis A 47 tokens
- Agent explorer A 47 tokens
- Agent momus A 49 tokens
- Agent reviewer A 43 tokens
- Hook PostToolUse A not measured
- MCP server ast_grep A not measured
- MCP server lsp A not measured
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 · 36 lines scan A ea241abb9cd6
omo is a plugin published in the GitHub repository code-yeongyu/lazyclaudecode (18 stars, last pushed 4mo 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-08-30.
Other plugins, from other repositories
hush
Quieter sessions for Claude Code: less narration, shorter tool output and concise answers focused on the result.
fable-baton
Turns Fable 5 into a token-frugal orchestrator: Fable keeps judgment, tiered Opus/Sonnet/Haiku agents do the labor.
ballast
Builds up to a goal in a field you have no expertise in: splits it into the foundations that goal actually needs, mobilizes what you already hold, learns what is missing, and leaves every solved path behind for the next goal. Nothing is called done until a check passes.
razor
Reuse-first checks for Claude Code: reconsider dependencies, file growth and unnecessary code before adding more.
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.
lsp-bench
Test, validate, and benchmark performance of LSP servers using only YAML. Configs for benchmarks, response assertions, multi-file consistency checks, file-edit sequences, lifecycle tests, version comparisons, and LSP session management — restart per benchmark (cold) or reuse one initialized session across steps (warm).