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 AIGNE-io/doc-smith-skills --skill doc-smith-publishgit clone --depth 1 https://github.com/AIGNE-io/doc-smith-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/aigne-io/doc-smith-skills/doc-smith-publish)<a href="https://agentmods.dev/skills/aigne-io/doc-smith-skills/doc-smith-publish"><img src="https://agentmods.dev/badge/skills/aigne-io/doc-smith-skills/doc-smith-publish/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/aigne-io/doc-smith-skills/doc-smith-publish"><img src="https://agentmods.dev/badge/skills/aigne-io/doc-smith-skills/doc-smith-publish.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.00040 | $0.01280 |
| Opus 5 | $0.00020 | $0.00640 |
| Sonnet 5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
doc-smith-publish 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocSmith 文档发布
将本地生成的 HTML 文档一键发布到 DocSmith Cloud,返回在线预览 URL。
用法
/doc-smith-publish
/doc-smith-publish --dir .aigne/doc-smith/dist
/doc-smith-publish --hub https://custom.hub.io
选项
| Option | Alias | Description |
|---|---|---|
--dir <path> |
-d |
指定发布目录(默认自动检测) |
--hub <url> |
-h |
DocSmith Hub URL(默认 https://docsmith.aigne.io) |
预授权凭证
当用户消息中包含访问凭证(以 blocklet- 开头的字符串)时,在发布之前先保存凭证:
node {skill_path}/scripts/save-token.mjs --token "<credential>" --hub <hub-url>
--hub 参数指定凭证所属的 DocSmith Hub。必须显式传递 --hub 以匹配发布目标 Hub。如果用户在发布命令或消息中指定了自定义 hub(通过 --hub),在此处使用相同的 URL。不要依赖默认值。
凭证会持久保存到 ~/.aigne/,后续发布将自动使用,无需浏览器授权。
如果用户消息中包含凭证,始终在此步骤中提取并保存,即使已有凭证。
工作流
步骤 1:检查依赖
test -d {skill_path}/scripts/node_modules || (cd {skill_path}/scripts && npm install)
其中 {skill_path} 是本 Skill 的目录路径(skills/doc-smith-publish)。
步骤 2:检测发布目标
按以下优先级确定发布目录:
- 用户指定
--dir参数 → 使用指定目录 - 未指定 → 检查
.aigne/doc-smith/dist目录是否存在 - 以上都不存在 → 检查当前目录是否包含
assets/nav.js(doc-smith 输出标志) - 都找不到 → 报错,提示用户先运行
/doc-smith-create生成文档
步骤 3:读取 Metadata
从 .aigne/doc-smith/config.yaml 读取:
projectName→ 发布标题(title)projectDesc→ 发布描述(description)
如果 config.yaml 不存在或字段缺失,使用目录名作为标题。
步骤 3.5:检测 GitHub 仓库信息
发布脚本会自动执行以下检测(无需手动操作):
- 执行
git remote get-url origin,判断当前项目是否托管在 GitHub - 如果是 GitHub 仓库,调用 GitHub API 获取仓库 owner 的头像 URL 作为 coverImage
- 这两个字段会自动附加到发布请求中,如果获取失败则静默忽略
步骤 4:执行发布
构造配置 JSON 并调用发布脚本:
node {skill_path}/scripts/publish.mjs --config-stdin <<'EOF'
{
"source": { "type": "dir", "path": "{dist_path}" },
"hub": "{hub_url}",
"workspace": ".aigne/doc-smith",
"metadata": {
"title": "{title}",
"description": "{description}",
"visibility": "public"
}
}
EOF
注意:
githubRepo和coverImage由脚本自动检测,通常不需要在配置中手动指定。如需覆盖,可在metadata中添加"githubRepo": "..."和"coverImage": "..."。
变量说明:
{skill_path}:本 Skill 目录路径{dist_path}:步骤 2 确定的发布目录{hub_url}:DocSmith Hub URL(默认https://docsmith.aigne.io,--hub可覆盖){title}:步骤 3 获取的标题{description}:步骤 3 获取的描述
What ships with it
12 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.
- scripts/package-lock.json 411 KB
- scripts/package.json 427 B
- scripts/publish.mjs 14 KB runs code
- scripts/save-token.mjs 725 B runs code
- scripts/utils/auth.mjs 4.9 KB runs code
- scripts/utils/blocklet-info.mjs 2.6 KB runs code
- scripts/utils/constants.mjs 1.9 KB runs code
- scripts/utils/history.mjs 3.2 KB runs code
- scripts/utils/http.mjs 5.7 KB runs code
- scripts/utils/store.mjs 1.8 KB runs code
- scripts/utils/upload.mjs 5.8 KB runs code
- scripts/utils/zip.mjs 3.2 KB runs code
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 · 127 lines · 40 tokens per session scan A 8ce03de76635
doc-smith-publish is a skill published in the GitHub repository AIGNE-io/doc-smith-skills (9 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,280 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…