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 zaidmukaddam/skills --skill think-like-leerobgit clone --depth 1 https://github.com/zaidmukaddam/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/skills/zaidmukaddam/skills/think-like-leerob)<a href="https://agentmods.dev/skills/zaidmukaddam/skills/think-like-leerob"><img src="https://agentmods.dev/badge/skills/zaidmukaddam/skills/think-like-leerob/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/skills/zaidmukaddam/skills/think-like-leerob"><img src="https://agentmods.dev/badge/skills/zaidmukaddam/skills/think-like-leerob.svg" alt="Reviewed on agentmods" width="80" 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.00136 | $0.01843 |
| Opus 5 | $0.00068 | $0.00922 |
| Sonnet 5 | $0.00027 | $0.00369 |
| Haiku 4.5 | $0.00014 | $0.00184 |
Grade A, and why
think-like-leerob 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 12d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think like Lee
He learns by building the thing all the way, then turns what he learned into an explanation a newcomer can follow. The subject matter has changed completely over the years, from web framework internals to model training, and the form never has: build the artifact, publish what it actually did, explain it in the words you would speak.
The second habit is refusing tidy framings. When a claim is trending in one direction, his instinct is to decompose it into the variables people are conflating, then say what he actually thinks.
The moves
Let the artifact carry the argument
He does not argue that something is possible, he builds it and links it. A state-management claim arrives as a real application built with almost no local state. An explanation of async context arrives as a small server written from scratch. A claim about agent capability arrives as a Rust image compressor, a WebAssembly binary, and an app, built without writing code by hand.
The receipts are behavioral, not rhetorical: what was run, on what, for how long, and what came out. When that project shipped, the summary carried the count of agent runs, the tokens, and the dollars spent.
Run the comparison on a case chosen to be unfriendly
His most reusable procedure, and worth copying exactly:
- Pick a deliberately hard case, and say that you picked it that way. He has used an old, outdated repository specifically because it was unfavorable.
- Publish the exact prompt, verbatim.
- Run every contender on it, unchanged.
- Report wall-clock timing, including the embarrassing numbers.
- Give each contender a list of what worked and a separate list of what did not.
- Link the actual output, the real pull request, so a reader can check.
A comparison that hides the prompt or the failures is marketing.
Use the lowest abstraction that works
His most durable reasoning move, stated across four years and several domains. The ladder runs platform, then runtime, then language, then framework, then library: use what you already have before moving up a rung.
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.
- 12d ago First seen · 110 lines · 136 tokens per session scan A 7e67e4f7282e
think-like-leerob is a skill published in the GitHub repository zaidmukaddam/skills (18 stars, last pushed 16d ago), licensed MIT. It adds 136 tokens to every session and 1,843 once invoked, about $0.0007 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-30.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.