Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/seite-sh/seitenpx agentmods add commands/seite-sh/seite/articleWrote 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/article)<a href="https://agentmods.dev/commands/seite-sh/seite/article"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/article/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/article"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/article.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.04189 |
| Opus 5.5 | $0.00000 | $0.01676 |
| Sonnet 5.5 | $0.00000 | $0.00838 |
| Haiku 4.5 | $0.00000 | $0.00419 |
Grade A, and why
article 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.
This is a copy
86% identical to article — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Article Command
A unified content creation pipeline that produces comprehensive, SEO-optimized articles through mandatory research, strategic planning, and section-by-section writing.
Usage
/article [topic]
Examples:
/article "Best Project Management Tools for Small Teams"/article "Content Marketing Strategy Guide 2025"/article "How to Migrate from Competitor to Your Product"
What This Command Does
Creates high-quality articles by enforcing a 4-step pipeline where research is mandatory, not optional:
STEP 1: SERP Analysis → See what Google rewards TODAY
STEP 2: Social Research → Mine Reddit + YouTube for real insights
STEP 3: Article Planning → Section-by-section strategy
STEP 4: Section Writing → Write/edit each section individually
This prevents the "AI knows everything" trap that produces generic content matching competitors instead of beating them.
When to Use This vs /write
| Scenario | Command |
|---|---|
| Comprehensive new article | /article |
| Competitive topics | /article |
| Topics where you need to beat existing content | /article |
| Quick drafts from existing research | /write |
| Simple updates to existing content | /write |
STEP 1: SERP Analysis (MANDATORY)
You MUST research before writing. No exceptions.
Process
-
Search the Target Keyword Use WebSearch to find what's currently ranking:
WebSearch: "[topic] industry" OR "[topic] industrying" -
Analyze Top 5 Ranking Articles For each top-ranking article, use WebFetch and document:
Element What to Capture Structure H2 headings, section order, content type Word Count Approximate length Gaps Topics covered superficially (<150 words) Missing Angles Perspectives not addressed Unsupported Claims Statements without data/sources Outdated Info Old statistics, deprecated tools What They Do Well Strong sections to match
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 · 604 lines · 0 tokens per session scan A 60e2808ab021
article 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 4,189 tokens. A static security scan graded it A with 0 findings. It is 86% identical to article, differing in 21 lines, and is treated as a copy.
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.