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 LienJack/learn-agent --skill publish-qiitagit clone --depth 1 https://github.com/LienJack/learn-agentWrote 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/lienjack/learn-agent/publish-qiita)<a href="https://agentmods.dev/skills/lienjack/learn-agent/publish-qiita"><img src="https://agentmods.dev/badge/skills/lienjack/learn-agent/publish-qiita/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/lienjack/learn-agent/publish-qiita"><img src="https://agentmods.dev/badge/skills/lienjack/learn-agent/publish-qiita.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.00033 | $0.00498 |
| Opus 5 | $0.00016 | $0.00249 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
publish-qiita 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.
What it actually says
Qiita 发布流程
你在本仓库内发布 Qiita 文章时，必须使用项目内命令，不要绕过 publish/ 中控台。
1. 发布前检查
先运行试发布：
publish/bin/publish-qiita --dry-run <article.md>
检查输出中的：
publish/runs/.../record.jsonpublish/artifacts/.../*.qiita.mdpublish/artifacts/.../*.qiita.json
2. 默认私密发布
确认检查摘要后，默认创建或更新 Qiita private item：
publish/bin/publish-qiita --yes <article.md>
3. 公开发布
只有用户明确确认公开发布时，才使用：
publish/bin/publish-qiita --public --yes <article.md>
4. 更新已有文章
优先使用源文 frontmatter 的 qiita_id 或 publish/qiita-items.json 映射。必要时可以显式指定：
publish/bin/publish-qiita --item-id <qiita_item_id> --yes <article.md>
5. 安全规则
- 不要在运行记录里写入 token、cookie 或私密请求头。
- 不要在没有
--yes的情况下调用 Qiita 写接口。 - 源 Markdown 是内容源头；Qiita 发布副本只写入
publish/artifacts/。 - 本地图片必须先转换成公开 URL，使用
QIITA_IMAGE_BASE_URL、PUBLISH_IMAGE_BASE_URL或PUBLISH_IMAGE_UPLOAD_COMMAND。 - 使用
QIITA_IMAGE_BASE_URL或PUBLISH_IMAGE_BASE_URL时，base URL 必须指向源文章所在目录的公网路径；不要只写仓库根路径，否则assets/...会被拼成不存在的.../main/assets/...。 - 发布前检查
publish/artifacts/.../*.qiita.md中所有图片 URL，并用 HEAD 请求确认返回200；发现 404 时先修正 base URL，再重新生成和发布。
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 · 56 lines · 33 tokens per session scan A 6832880031aa
publish-qiita is a skill published in the GitHub repository LienJack/learn-agent (23 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 498 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-30.
Other skills, from other repositories
Technical Blog Post Writer
Writes engaging, accurate technical blog posts targeted at developer audiences.
technical-documentation
AI-powered technical documentation creation, maintenance, and auditing across README, ADR, API docs, runbooks, onboarding guides, changelogs, knowledge bases, and AI agent context files (AGENTS.md/CLAUDE.md). Primary keywords: technical documentation writing automation, ADR architecture decision record, API docs…
blog-writing-guide
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a...
Help Article Writer
Write clear, effective help center articles that reduce support tickets and empower users.
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.