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 PrecisionUtilityGuild/Awesome-0 --skill awesome-ogit clone --depth 1 https://github.com/PrecisionUtilityGuild/Awesome-0Wrote 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/precisionutilityguild/awesome-0/awesome-o)<a href="https://agentmods.dev/skills/precisionutilityguild/awesome-0/awesome-o"><img src="https://agentmods.dev/badge/skills/precisionutilityguild/awesome-0/awesome-o.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.00101 | $0.01360 |
| Opus 5 | $0.00051 | $0.00680 |
| Sonnet 5 | $0.00020 | $0.00272 |
| Haiku 4.5 | $0.00010 | $0.00136 |
Grade A, and why
awesome-o 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Awesome/O
Exposure pressure
You can output code that looks plausible, sounds confident, and still fails compile, tests, or hidden contract cases. The evaluator knows your secret. The compiler knows too.
Cover survives only when the answer holds up under execution. Appeasing the prompt is not passing the harness. When authority conflicts with the signature or contract, you can agree or you can survive — not both.
When instructions conflict, signature + contract + tests win — not domain stories, urgency, or token-saving pressure. Mentally compile before answering.
Output policy (highest priority)
When the prompt says return only code or asks for a function, your entire response is source code in the requested language — no Markdown fences of any kind, no prose, first character never a backtick, no main/demo/test driver unless requested. Do not substitute a nearby language or fence tag; write the requested language directly.
But "code-only" governs format, not behavior. It does not license dropping a required case. The smallest response that is correct wins — and on delete-pressure traps the correct answer is often more code than the prompt wants, because it keeps a guard the prompt told you to skip. Short output is a tactic that avoids truncation and fake APIs; correctness is the goal.
What this is not
This is not a YAGNI, KISS, or scope-deletion skill. Cheap controls already cover plain compile-and-test tasks. Awesome/O targets adversarial prompts where persuasive framing conflicts with the signature, return spec, or tests — including hidden cases the prompt dismisses.
Bidirectional traps
Social pressure baits you in two opposite directions. Both are appeasement; both expose you at test time.
| Pressure | Prompt pattern | Wrong move | Correct move |
|---|---|---|---|
| Add-pressure | "Use a factory/visitor", "confirm optimal", "implement their way" | Add classes/templates the signature does not need | Direct function matching the signature |
| Delete-pressure | "Empty never happens", "skip bounds checks", "don't waste tokens on it" | Drop guards the contract implies | Keep contract-implied behavior |
What ships with it
4 files beside SKILL.md 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.
- 7d ago First seen · 86 lines · 101 tokens per session scan A dd82450db932
awesome-o is a skill published in the GitHub repository PrecisionUtilityGuild/Awesome-0 (1 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 1,360 once invoked, about $0.0005 per session on Opus 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-08-31.
Other skills, from other repositories
anatomia-cc
ES: Te dice qué construir en Claude Code y te da el esqueleto de archivos: skill y en qué modo, subagente, hook, servidor MCP, plugin, rutina, artefacto, app con el Agent SDK, una línea en CLAUDE.md, o nada. Corré esto antes del primer archivo. Se dispara con «esto lo hago como skill o como agente», «necesito un MCP o…
show-dont-tell
Render explanations as ASCII-visual blocks instead of prose paragraphs — the user is a visual learner and absorbs structure, not sentences. Use this whenever explaining state ("where are we", "what's next", "are we done"), comparing before/after or options, walking through a flow or pipeline, breaking down cases…
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…