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 agentmods add instructions/grisuno/lazyown/claude-mdgit clone --depth 1 https://github.com/grisuno/LazyOwnWrote 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/instructions/grisuno/lazyown/claude-md)<a href="https://agentmods.dev/instructions/grisuno/lazyown/claude-md"><img src="https://agentmods.dev/badge/instructions/grisuno/lazyown/claude-md.svg" alt="Measured on agentmods" 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.11032 | $0.11032 |
| Opus 5 | $0.05516 | $0.05516 |
| Sonnet 5 | $0.02206 | $0.02206 |
| Haiku 4.5 | $0.01103 | $0.01103 |
Grade A, and why
LazyOwn CLAUDE.md scanned grade A with 2 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# CLI: collab_join <handle> [--curl] Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Long-running tool → never timeout below documented runtime (e.g. `lazynmap` ≥ 30 min); detach via `subprocess.Popen`, `print_msg` w/ artefact path. The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- yesterday Changed · +4 lines · +87 tokens per session a4ac4f159bad
- 6d ago First seen · 617 lines · 10,945 tokens per session scan A 35562674d695
LazyOwn CLAUDE.md is an instructions file published in the GitHub repository grisuno/LazyOwn (225 stars, last pushed yesterday), licensed GPL-3.0. It adds 11,032 tokens to every session, about $0.0552 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
sdrf-skills GEMINI.md
Instructions for bigbio/sdrf-skills, covering sdrf-skills — sdrf annotation skills, available workflows, specification data and key rules.
react-flow-skill CLAUDE.md
Instructions for framara/react-flow-skill, covering claude.md, what this repo is, repository structure and editing guidelines.
campy AGENTS.md
Instructions for dropdevrahul/campy, covering campy - opencode pets plugin, project overview, available pets, file structure and commands.
interactive-process-mcp CLAUDE.md
Instructions for UserB1ank/interactive-process-mcp, covering security & privacy, agent skills, issue tracker, triage labels and domain docs.
visuals-mcp copilot-instructions.md
Copilot instructions for harrybin/visuals-mcp, covering mcp table server - copilot instructions, project overview, architecture, components and data flow.
mcpexplained AGENTS.md
Instructions for reachjalil/mcpexplained: This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in nodemodules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root)…