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 agentmods add commands/seite-sh/seite/writegit clone --depth 1 https://github.com/seite-sh/seiteWhat 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 | $0.00000 | $0.03562 |
| Opus 5 | $0.00000 | $0.01781 |
| Sonnet 5 | $0.00000 | $0.00712 |
| Haiku 4.5 | $0.00000 | $0.00356 |
Grade A, and why
write 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 2d 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
92% identical to write — 50 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Command
Use this command to create comprehensive, SEO-optimized long-form blog content.
Usage
/write [topic or research brief]
What This Command Does
- Creates complete, well-structured long-form articles (2000-3000+ words)
- Optimizes content for target keywords and SEO best practices
- Maintains your brand voice and messaging throughout
- Integrates internal and external links strategically
- Includes all meta elements for publishing
Process
Pre-Writing Review
- Research Brief: Review research brief from
/researchcommand if available - Brand Voice: Check @context/brand-voice.md for tone and messaging
- Writing Examples: Study @context/writing-examples.md for style consistency
- Style Guide: Follow formatting rules from @context/style-guide.md
- SEO Guidelines: Apply requirements from @context/seo-guidelines.md
- Target Keywords: Integrate keywords from @context/target-keywords.md naturally
Content Structure
1. Headline (H1)
- Include primary keyword naturally
- Create compelling, click-worthy title
- Keep under 60 characters for SERP display
- Promise clear value to reader
2. Introduction (150-200 words)
CRITICAL: The Hook (First 1-2 Sentences)
The opening hook is the most important element. A strong hook can boost reader retention by 30%. NEVER open with a generic definition or statement like "X is..." or "When it comes to..."
Choose ONE hook type for each article:
| Hook Type | Example | Best For |
|---|---|---|
| Provocative Question | "What if the 'free' plan is actually costing you $500/month in lost opportunities?" | Challenging assumptions |
| Specific Scenario | "Last Tuesday, Sarah checked her dashboard and discovered something alarming: her site had been invisible to Google for three weeks." | Creating emotional connection |
| Surprising Statistic | "73% of SaaS users who switch platforms do so within 18 months, and most cite the same three reasons." | Data-driven topics |
| Bold Statement | "Your current tool is lying to you about your numbers." | Controversial takes |
| Counterintuitive Claim | "The cheapest option might be the most expensive decision you make this year." | Comparison content |
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.
- 2d ago First seen · 355 lines · 0 tokens per session scan A ade3d15d6fb2
write is a command published in the GitHub repository seite-sh/seite (19 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,562 tokens. A static security scan graded it A with 0 findings. It is 92% identical to write, differing in 50 lines, and is treated as a copy.
Other commands, from other repositories
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
wiki-init
Initialize a new LLM Wiki in the current directory. Creates the full directory structure, config, and template files.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.