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 LeaYeh/skills --skill bloggit clone --depth 1 https://github.com/LeaYeh/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/leayeh/skills/blog)<a href="https://agentmods.dev/skills/leayeh/skills/blog"><img src="https://agentmods.dev/badge/skills/leayeh/skills/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/leayeh/skills/blog"><img src="https://agentmods.dev/badge/skills/leayeh/skills/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.00099 | $0.00939 |
| Opus 5 | $0.00049 | $0.00469 |
| Sonnet 5 | $0.00020 | $0.00188 |
| Haiku 4.5 | $0.00010 | $0.00094 |
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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog
Distill the value and insight of the current session into a public technical article, co-written through interview, then stage it as a bilingual Hugo draft. This is a flexible, conversational skill — never auto-publish.
Discussion in Traditional Chinese (zh-TW); article content in both zh-TW and English.
Blog location
Default Hugo source: ~/project/git_dev/lyeh-infra/apps/portal/src (posts in content/posts/).
If that path does not exist, ask the user for the blog repo path before writing anything.
Workflow
1. Free description
Ask the user to describe, in their own words, what they found valuable about this session. Let them ramble — do not interrupt with questions yet.
2. Mine the session
Review the actual conversation/session context and pre-fill a draft of these dimensions. Show the user what you extracted so they can correct it:
- Hook — the problem or itch that drove this; why a reader should care
- Context — the setup, constraints, what was tried before
- Turning point / core insight — the non-obvious thing learned (the heart of the post)
- How it works — the concrete solution, with code/config snippets where they earn their place
- Trade-offs / what I'd do differently — the honesty that makes it credible
- Takeaway — what the reader should remember and can reuse
3. Interview to fill gaps
Interview the user one question at a time, grill-me style, only on the dimensions still thin or ambiguous after step 2. For each question, offer your recommended answer. Goal: sharpen the angle and surface the insight — not interrogate the design. Stop when the six dimensions are solid and the article's spine is clear.
4. Converge on an outline
Propose a title + section outline. Get a thumbs-up before drafting full prose.
5. Write the bilingual draft
Write the English post first, then the zh-TW translation (idiomatic, not literal — adapt examples and phrasing for a Chinese-reading developer). See PUBLISHING.md for exact front matter, file naming, and the one-time i18n setup.
What ships with it
1 file 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.
- 8d ago First seen · 59 lines · 99 tokens per session scan A cfd8ae1530d9
blog is a skill published in the GitHub repository LeaYeh/skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 939 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
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.