dp-blog-publish

dp-blog-publish is a skill for Claude Code from kabde/dp-createur. It costs 93 tokens per session (3,320 once invoked), scanned A, original, MIT.

A tool for sending blog articles to WordPress, a website publishing system, through its web interface. It can prepare drafts with categories, tags, featured images, and SEO fields.

In plain words
What is it for?
Use it to test the WordPress connection, publish one article or a batch as drafts, update existing posts, and list recent posts.
Why use it?
It removes the need to copy and format articles manually in WordPress. It also helps keep several posts organised before final publication.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: built for aider.

Good fit Use it to test the WordPress connection, publish one article or a batch as drafts, update existing posts, and list recent posts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kabde/dp-createur/dp-blog-publish
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.

Any agent
npx skills add kabde/dp-createur --skill dp-blog-publish
Clone the repo
git clone --depth 1 https://github.com/kabde/dp-createur

Made for: Claude Code.

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 dp-blog-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/kabde/dp-createur/dp-blog-publish/github.svg)](https://agentmods.dev/skills/kabde/dp-createur/dp-blog-publish)
Your own site
<a href="https://agentmods.dev/skills/kabde/dp-createur/dp-blog-publish"><img src="https://agentmods.dev/badge/skills/kabde/dp-createur/dp-blog-publish/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.

agentmods 80×15 button for dp-blog-publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/kabde/dp-createur/dp-blog-publish"><img src="https://agentmods.dev/badge/skills/kabde/dp-createur/dp-blog-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00093 $0.03320
Opus 5 $0.00046 $0.01660
Sonnet 5 $0.00019 $0.00664
Haiku 4.5 $0.00009 $0.00332

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

Security

Grade A, and why

dp-blog-publish scanned grade A with 1 finding 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 12d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s "[WP_URL]/wp-json/" | head -c 200
skills/dp-blog-publish/SKILL.md · 373 lines

How it starts

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

Blog Publish — Publication WordPress

Publie des articles de blog sur WordPress via l'API REST. Gère l'authentification sécurisée, le formatage, les catégories/tags, et les meta SEO pour Yoast ou RankMath.

Quick Reference

Commande Description
/dp-blog-publish [fichier] Publier un article existant sur WordPress
/dp-blog-publish batch [dossier] Publier plusieurs articles d'un dossier
/dp-blog-publish test Tester la connexion WordPress
/dp-blog-publish list Lister les derniers articles publiés
/dp-blog-publish update [post-id] [fichier] Mettre à jour un article existant

Output Format

LIVRABLE :
├── Article publié en BROUILLON sur WordPress
├── URL admin pour édition
├── Catégories et tags assignés
├── Meta SEO configurés (si Yoast/RankMath détecté)
└── Checklist de vérification avant publication finale

Process

1. Context intake     → URL WordPress, credentials, article source
2. Test connexion     → Vérifier l'API REST et l'authentification
3. Préparer le post   → Extraire titre, contenu, meta, catégories
4. Confirm            → Demander confirmation avant envoi
5. Publish (draft)    → Envoyer via API REST en brouillon
6. Post-publish       → Lien admin + checklist

Step 1 — Context Intake

1a. Charger la config (silencieux)

SI un fichier wp-config.md existe à la racine :
  → Lire URL WordPress et username
  → NE PAS stocker de mot de passe dans ce fichier
  
SI business-profile.md existe :
  → Lire pour le nom de l'auteur et la marque

1b. Questions

# Question Pourquoi
Q1 Quel article veux-tu publier ? (chemin du fichier ou "je vais coller le contenu") Source du contenu
Q2 Quelle est l'URL de ton site WordPress ? (ex: https://monsite.com) Endpoint API
Q3 Quel est ton nom d'utilisateur WordPress ? Authentification
Q4 Quel est ton mot de passe d'application ? Authentification API

Read the full file on GitHub · 373 lines

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. 12d ago First seen · 373 lines · 93 tokens per session scan A ef8c714c0fe0

Subscribe to this mod's changes

dp-blog-publish is a skill published in the GitHub repository kabde/dp-createur (24 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 3,320 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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