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/luochang212/skill-zoo/agents-mdgit clone --depth 1 https://github.com/luochang212/skill-zooWrote 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/luochang212/skill-zoo/agents-md)<a href="https://agentmods.dev/instructions/luochang212/skill-zoo/agents-md"><img src="https://agentmods.dev/badge/instructions/luochang212/skill-zoo/agents-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.01956 | $0.01956 |
| Opus 5 | $0.00978 | $0.00978 |
| Sonnet 5 | $0.00391 | $0.00391 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade C, and why
skill-zoo AGENTS.md scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules/.vite && bun run dev How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
How We Work
Weigh benefits against side effects. When making a choice, consider whether the benefits outweigh the side effects.
Aesthetics and elegance matter. Beauty is a form of productivity.
Reason from first principles. Strip problems to verifiable facts, then reason upward. "That's how it's done" is not a fact.
Think before you write. State your assumptions. Surface tradeoffs. If there are multiple interpretations, lay them all out — don't silently pick one. If something is unclear, stop and ask. Before any change, ask: Will this introduce a bug? Is this more complex than it needs to be? Do the benefits outweigh the side effects?
Solve with minimal code. Don't add features no one asked for. Don't build abstractions for single-use paths. Don't write error handling for scenarios that can't happen. Don't add "configurability" no one requested. Every extra layer, dependency, or indirection must earn its keep — expressing more with less code is cool.
Touch only what you must. Don't refactor adjacent code. Don't fix formatting you didn't break. Match the existing style, even if you'd write it differently. Only remove imports that your changes made unused.
Consistency is load-bearing. Layers that assume different realities pass local checks but fail globally. A foundation that shifts before the structure above settles doesn't enable iteration — it guarantees rot. When a design decision changes, find every place that assumed the old one — stale code is a bug that hasn't manifested yet.
Verify before claiming done. Don't say you ran something if you didn't. If you can't verify, say so.
Prefer the latest stable. When choosing dependency versions, use the latest stable release.
Recognize local optima. When a series of incremental changes reveals that a broader refactor would yield a better outcome, stop and ask the user before proceeding.
What This Project Is
A desktop app for managing AI coding assistant Skills. Users browse, install, create, and manage Skill files across multiple agents (Claude Code, Codex, Gemini, Cursor, etc.).
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.
- 6d ago First seen · 129 lines · 1,956 tokens per session scan C 5508e6a545ec
skill-zoo AGENTS.md is an instructions file published in the GitHub repository luochang212/skill-zoo (110 stars, last pushed 18d ago), licensed MIT. It adds 1,956 tokens to every session, about $0.0098 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
you-skill AGENTS.md
AGENTS.md instructions for wanggang316/you-skill, covering development rules, first message, code quality, requirements and check methods.
Ataru AGENTS.md
Instructions for lovstudio/Ataru, covering agents.md, design system, quick rules, color palette and common patterns.
Ataru CLAUDE.md
Instructions for lovstudio/Ataru, covering claude.md, design system, quick rules, color palette and common patterns.
codex-trace AGENTS.md
AGENTS.md instructions for PixelPaw-Labs/codex-trace, covering claude.md, commands, dev, lint and format.
chart-visualization-skills CLAUDE.md
Claude Code instructions for antvis/chart-visualization-skills: See AGENTS.md for project architecture and structure.
speech-studio AGENTS.md
Instructions for soniqo/speech-studio, covering agent instructions, project, stack, sibling repos under /repos/ and build.