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 lsh1215/oh-my-study-with-me --skill bloggit clone --depth 1 https://github.com/lsh1215/oh-my-study-with-meWrote 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/lsh1215/oh-my-study-with-me/blog)<a href="https://agentmods.dev/skills/lsh1215/oh-my-study-with-me/blog"><img src="https://agentmods.dev/badge/skills/lsh1215/oh-my-study-with-me/blog/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/lsh1215/oh-my-study-with-me/blog"><img src="https://agentmods.dev/badge/skills/lsh1215/oh-my-study-with-me/blog.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.00046 | $0.02584 |
| Opus 5 | $0.00023 | $0.01292 |
| Sonnet 5 | $0.00009 | $0.00517 |
| Haiku 4.5 | $0.00005 | $0.00258 |
Grade A, and why
blog 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 11d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog - Technical Blog Writing Skill
Argument: $ARGUMENTS
Writing Philosophy
The writing in this skill is grounded in the following principles. Apply them at every stage.
1. Writing is the process of completing thought
"Writing about something, even something you know well, usually reveals that you didn't know it as well as you thought." — Paul Graham
It is natural for a first draft to be a mess. The thinking is not yet complete. Writing is how thought gets organized. Therefore, the correct order is not "understand perfectly, then write" — it is "write to complete the understanding."
2. Clarity is an ethical choice
"The great enemy of clear language is insincerity." — George Orwell
Writing vaguely is deceiving the reader. In technical writing, phrases like "handled appropriately" or "works efficiently" say nothing. Write concretely. Write in measurable terms.
3. Simplicity is not simple thinking
"The secret of good writing is to strip every sentence to its cleanest components." — William Zinsser
Writing complex ideas simply is the hardest thing of all. Stripping clutter does not mean reducing content — it means making the content more visible.
4. Intellectual honesty creates persuasion
"A theory that is not refutable by any conceivable event is non-scientific." — Karl Popper
Writing that exposes the weaknesses of its own argument earns more trust. "This is the best approach" is weaker than "I chose this approach because of X. That said, in Y situations, Z is more appropriate." That is the language of an expert.
Style Rules
Plain sentences
- Avoid figurative language. Use concrete examples and data instead of metaphors.
- ❌ "Kafka is the highway of data"
- ✅ "Kafka stores and delivers messages in order between producers and consumers"
- Question every modifier. Ask every adjective and adverb: "Why are you here?"
- ❌ "Processed very quickly"
- ✅ "Processed within 47ms at the P99 latency threshold"
- Write in active voice. Do not hide the actor.
- ❌ "The configuration was changed"
- ✅ "The producer changes the acks setting to all"
- Never use a long word where a short one will do. (Orwell's Rule 2)
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.
- 11d ago First seen · 277 lines · 0 tokens per session scan A 659fe93e0eca
blog is a skill published in the GitHub repository lsh1215/oh-my-study-with-me (8 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 2,584 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…