agentmods.dev

wiki-draft

wiki-draft is a skill for Claude Code, Codex from PLATZDORSCH/wiki-hermes. It costs 27 tokens per session (604 once invoked), scanned A, original, MIT.

A skill for drafting blogs, newsletters, briefings, LinkedIn posts, or slides from information stored in an internal wiki. It selects relevant pages and a matching content template before saving a draft.

In plain words
What is it for?
Use it to turn wiki research into a content draft, choose the right format, add source references and front matter, and flag areas that need review.
Why use it?
It gives content work a repeatable source-and-template process. This reduces the chance of writing from incomplete wiki information or losing track of which pages support the draft.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 10 5mo ago A scan 27 tokens original MIT
View the source file PLATZDORSCH/wiki-hermes platzdorsch.de
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/platzdorsch/wiki-hermes/wiki-draft
Any agent
npx skills add PLATZDORSCH/wiki-hermes --skill wiki-draft
Clone the repo
git clone --depth 1 https://github.com/PLATZDORSCH/wiki-hermes

Made for: Claude Code, Codex.

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

agentmods badge for wiki-draft

README.md
[![agentmods](https://agentmods.dev/badge/skills/platzdorsch/wiki-hermes/wiki-draft.svg)](https://agentmods.dev/skills/platzdorsch/wiki-hermes/wiki-draft)
Your own site
<a href="https://agentmods.dev/skills/platzdorsch/wiki-hermes/wiki-draft"><img src="https://agentmods.dev/badge/skills/platzdorsch/wiki-hermes/wiki-draft.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 604 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.1 $0.00027 $0.00604
Opus 5 $0.00014 $0.00302
Sonnet 5 $0.00005 $0.00121
Haiku 4.5 $0.00003 $0.00060

Measured 6d ago against content hash 60076ff9d25a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

wiki-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 6d 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.

skills/wiki-draft/SKILL.md · 71 lines

What it actually says

wiki-draft

Erstelle einen Content-Entwurf auf Basis des Wiki-Wissens.

When to Use

  • User will einen Blogartikel, ein Briefing oder LinkedIn-Post schreiben
  • User sagt "schreib mir einen Artikel über...", "erstelle ein Briefing zu..." o.ä.

Procedure

  1. Thema und Format klären — Falls nicht eindeutig, kurz nachfragen. Mögliche Formate: blog, newsletter, briefing, linkedin, slides.

  2. Wiki durchsuchen — wiki/index.md lesen, relevante Seiten identifizieren und lesen. Besonders wiki/synthesis/ und wiki/trends/ prüfen.

  3. Template laden — Passendes Template aus content/templates/ laden:

    • content/templates/blog.md für Blogartikel
    • content/templates/newsletter.md für Newsletter
    • content/templates/briefing.md für Briefings
    • Für LinkedIn/Slides: freie Form

  4. Entwurf schreiben — In content/drafts/ mit Frontmatter:

    ---
title: "Titel des Contents"
format: blog
based_on: [wiki/trends/thema.md, wiki/topics/thema.md]
created: YYYY-MM-DD
status: draft
---

    Dateiname: YYYY-MM-DD-kurztitel.md

  5. User informieren — Entwurf dem User zeigen, auf Stellen hinweisen die Review brauchen.

  6. ⛔ Log schreiben — Eintrag in wiki/log.md:

    ## [YYYY-MM-DD] draft | Titel des Contents
- Format: blog
- Basiert auf: wiki/trends/..., wiki/topics/...
- Gespeichert: content/drafts/YYYY-MM-DD-kurztitel.md

Pitfalls

  • Entwürfe immer in content/drafts/, nie direkt in content/published/
  • Immer das Wiki als Basis nutzen, nicht frei erfinden
  • Quellenverweise einbauen wo möglich
  • Tonalität an die Zielgruppe anpassen
  • Log-Eintrag NIEMALS vergessen

Verification

⛔ BEVOR du den Workflow als abgeschlossen meldest:

  1. Entwurf existiert in content/drafts/
  2. Entwurf hat korrektes Frontmatter mit based_on-Verweisen
  3. wiki/log.md hat einen Draft-Eintrag
  4. Erst dann dem User Abschluss melden.
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. 6d ago First seen · 71 lines · 27 tokens per session scan A 60076ff9d25a

Subscribe to this mod's changes

wiki-draft is a skill published in the GitHub repository PLATZDORSCH/wiki-hermes (10 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 604 once invoked, about $0.0001 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.

Writing and docs
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

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…

microsoft/ai-agents-for-beginners · 200 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 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

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…

vercel/next.js · 83 tokens