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.
git clone --depth 1 https://github.com/seite-sh/seiteWrote 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/commands/seite-sh/seite/publish-draft)<a href="https://agentmods.dev/commands/seite-sh/seite/publish-draft"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/publish-draft/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/commands/seite-sh/seite/publish-draft"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/publish-draft.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.00000 | $0.00301 |
| Opus 5.5 | $0.00000 | $0.00120 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
publish-draft 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 1mo 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
Publish Draft — seite Edition
Publish a draft article from content/ by removing the draft: true flag, building the site, and optionally deploying.
Usage
/publish-draft <file-path>
Example: /publish-draft content/posts/2026-03-12-rust-error-handling.md
Workflow
- Read the specified file and verify it exists and has
draft: truein frontmatter - Run the content scrubber — check for AI watermarks and telltale patterns (same as SEOMachine's
/scrub). Fix any issues found - Remove
draft: truefrom the YAML frontmatter (or set it todraft: false) - Run
seite buildto verify the site builds successfully with the new content - Report the result — show the article title, URL it will be published at, and word count
- Ask if user wants to deploy — if yes, run
seite deploy
Important
- Do NOT use WordPress or any external CMS — this is a seite static site
- The article stays in its current location in
content/— seite serves it from there - After publishing, the article will appear at its URL (e.g.,
/posts/rust-error-handling) - Run
seite serveif the user wants to preview before deploying
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.
- 1mo ago First seen · 26 lines · 0 tokens per session scan A dde718945f08
publish-draft is a command published in the GitHub repository seite-sh/seite (25 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 tokens. 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 commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
install
This page explains how the livewiki install CLI command detects installed coding agents and safely configures the livewiki MCP server entry, hook templates, shared skills, and optional pointer files.
pointer
This page documents the livewiki pointer subcommand, which manages an opt-in "pointer" block inside an AGENTS.md or CLAUDE.md file at the repository root.
index-cmd
The index command reindexes a repository and synchronizes its anchor ledger while selecting human-readable, JSON, or quiet output.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
help
Get help with the hookify plugin.