agentmods.dev

publish

A publishing tool for ai-docs documents, which are paired Markdown and HTML files used for readable online documentation. It sends those files to a configured GitHub Pages repository.

In plain words
What is it for?
Use it to publish or update an ai-docs document, including a deck or postmortem, on the configured GitHub Pages site.
Why use it?
It provides a defined publishing path and checks that the destination is the configured repository, reducing the risk of sending a document to the wrong place.

Skill for Claude CodeCodex

6 3mo ago A scan 126 tokens original MIT
View the source file quantumentangled-dev/ai-docs-plugin
Install

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.

agentmods
npx agentmods add skills/quantumentangled-dev/ai-docs-plugin/publish
Any agent
npx skills add quantumentangled-dev/ai-docs-plugin --skill publish
Clone the repo
git clone --depth 1 https://github.com/quantumentangled-dev/ai-docs-plugin

Made for: Claude Code, Codex.

Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00126 $0.02408
Opus 5 $0.00063 $0.01204
Sonnet 5 $0.00025 $0.00482
Haiku 4.5 $0.00013 $0.00241

Measured yesterday against content hash a5c0542ed68e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/_config.sh, scripts/find-remote.sh, scripts/init-existing.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/publish/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

publish

Push a .md + .html pair to the configured GitHub Pages repo. Main thread owns the full flow — config detection, doc-type classification, remote search, user confirmation, and the publish.sh invocation. No subagent dispatch.

When to fire

Should trigger — publish: "publish it", "push to GitHub Pages", "deploy this deck", "ship the postmortem", "/ai-docs:publish".

Should trigger — update: "update the published version", "republish q2", "push the changes".

Should NOT trigger:

  • "create a deck about X" → create skill
  • "delete the deck" / "unpublish q2" → unpublish skill
  • "summarize this URL" → read skill
  • "publish my npm package" → unrelated; stop and clarify

Repo boundary

Publishes ONLY to the configured repo. Project-scope (<proj>/.ai-docs/config.json) overrides user-scope (~/.config/ai-docs/config.json) — walk-up matches closest .ai-docs/ marker dir from CWD. Refuse any non-configured repo.

Orchestration (main thread)

Phase A — config state

  1. CONFIG_PATH=$(${CLAUDE_PLUGIN_ROOT}/skills/publish/scripts/_config.sh path).
  2. test -s "$CONFIG_PATH" → present (read config: REPO, VISIBILITY, default_folders; continue to Phase C) or missing (Phase B first).

Read-only _config.sh commands are auto-allowed.

Phase B — setup (only when missing)

  1. gh auth status. Unauthenticated → surface "run gh auth login and re-trigger publish", STOP.
  2. AskUserQuestion: "Publish into an existing GitHub repo, or create a new one?" — options Use existing, Create new.

Existing:

  1. Pre-resolve OWNER=$(gh api user --jq .login) for the default suggestion.
  2. AskUserQuestion: "Which repo to publish into?" — options (must provide ≥2): Use <OWNER>/ai-docs (Recommended), Different owner/repo. The auto-added Other lets the user type a fully-custom <owner>/<repo>. Parse the resulting <owner>/<repo> from whichever option/text the user selected.
  3. gh api "repos/<owner>/<repo>" --jq '.full_name'. Nonzero → "Can't see <owner>/<repo> — check name + gh permissions", STOP.
  4. IS_PRIVATE=$(gh api "repos/<owner>/<repo>" --jq '.private'). true → private, false → public.
  5. ${CLAUDE_PLUGIN_ROOT}/skills/publish/scripts/init-existing.sh --owner <owner> --repo <repo> --visibility <vis>.

Read the full file on GitHub · 168 lines

Files

What ships with it

9 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.

Changes

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.

  1. yesterday First seen · 168 lines · 126 tokens per session scan A a5c0542ed68e

Subscribe to this mod's changes

publish is a skill published in the GitHub repository quantumentangled-dev/ai-docs-plugin (6 stars, last pushed 3mo ago), licensed MIT. It adds 126 tokens to every session and 2,408 once invoked, about $0.0006 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.

Backend and APIsDevOps and cloudDocuments
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens