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 atman-33/workhub --skill zenn-blog-writinggit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/zenn-blog-writing)<a href="https://agentmods.dev/skills/atman-33/workhub/zenn-blog-writing"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/zenn-blog-writing/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/atman-33/workhub/zenn-blog-writing"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/zenn-blog-writing.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.00095 | $0.01312 |
| Opus 5 | $0.00048 | $0.00656 |
| Sonnet 5 | $0.00019 | $0.00262 |
| Haiku 4.5 | $0.00010 | $0.00131 |
Grade A, and why
zenn-blog-writing 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zenn技術ブログ執筆スキル
Zennの技術記事を執筆・レビューする際の基準とワークフロー。技術的正確性、読みやすさ、AIっぽい文章の排除を重視する。
記事執筆のワークフロー
- 下書き作成:
published: falseで記事を作成 - 執筆: 本スキルのルールに従って記事を執筆
- ローカルチェック:
npm run textlintでチェック - プレビュー:
npm run previewでZenn CLIプレビュー - 修正: textlintの指摘を修正
- 公開準備:
published: trueに変更 - コミット: Git commit時に自動チェックが実行される
自動チェックコマンド
npm run textlint: 全記事をチェックnpm run textlint:fix: 全記事をチェックして自動修正可能な箇所を修正
フロントマター（必須）
---
title: "記事のタイトル" # 簡潔で具体的に
emoji: "😸" # 絵文字1文字のみ
type: "tech" # tech: 技術記事 / idea: アイデア記事
topics: ["tag1", "tag2"] # 3-5個、小文字で統一
published: false # false: 下書き / true: 公開
---
topicsのルール
記号やスペースは使えない。以下のように変換する:
| 技術名 | topics表記 |
|---|---|
| C++ | cpp |
| C# | csharp |
| .NET | dotnet |
| Node.js | nodejs |
| TypeScript | typescript |
| React Native | reactnative または react-native |
文章品質の基本ルール
書くとき
- 技術用語は正確に使い、初出時に説明を追加する
- コード例は動作確認済みのものを使う
- バージョン情報は明記する（例: Node.js v20.18.1）
- 1文は60文字以内を目安に、長文は分割する
- 受動態より能動態を優先（「〜されます」→「〜します」）
- 文章の末尾は必ず「。」で終わる（「：」は禁止）
避けるべきAIっぽい表現
- 過剰な強調（「重要」「注意」の連続使用）
- 誇張表現（「革命的」「驚異的」「完璧な」）
- 情報系プレフィックス（「重要:」「注意:」「警告:」）
- コロン後のブロック（「実行します:」→「実行方法は以下の通りです。」）
- 見出し内での太字
コードブロック
- 必ず言語を指定する（
bash,javascript,typescript,python,json等） - シェルコマンドは
bashを使用 - 変数名・関数名は意味のあるものにする
- コメントは日本語で簡潔に
マークダウン
- 見出しは
#########を論理的に階層化 - リストは箇条書き（
-）を使用 - 技術用語はコードフォーマット（
`text`）で囲む - 外部リンクは参照した記事・ドキュメントに必ず貼る
- リンクテキストは具体的に（「こちら」ではなく「公式ドキュメント」）
記事本文の推奨構成
- 導入部: 問題提起や背景（2-3段落）
- 本論: 技術的説明、手順、コード例
- まとめ: 要点整理と次のステップの提示
技術ブログとしての心構え
- 読者の視点: 実際に試せる内容を提供する
- 正確性: 技術情報は必ず確認してから記載する
- 継続性: 記事は定期的に更新・メンテナンスする
詳細リファレンス
- 詳細な文章ルール、コードブロック規則、マークダウン規則: WRITING-RULES.md
- レビュー時のチェックリスト全項目: REVIEW-CHECKLIST.md
参考資料
What ships with it
2 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.
- 8d ago First seen · 102 lines · 95 tokens per session scan A 41a4c71c7db2
zenn-blog-writing is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,312 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-09-03.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
教程类H5-小红书小工具
A method for building offline, single-page course experiences for Xiaohongshu’s Mini Tools, which are interactive pages published inside the platform. It combines written lessons, generated illustrations, and JavaScript page switching in a constrained container.
sansheng-distill
A book and text summarizer that creates one self-contained HTML page with five sections: an overview, chapter notes, the book’s central idea, an action checklist, and questions for judging its reliability. The page includes an embedded Mermaid mind map and works offline without a web server.
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
learn
Explain recent vibe-learn session activity or answer a question about what was built, grounded in .vibe-learn/session-log.jsonl.