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 skills/uluckyxh/openmoss/wordpress-skillnpx skills add uluckyXH/OpenMOSS --skill wordpress-skillgit clone --depth 1 https://github.com/uluckyXH/OpenMOSSWrote 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/skills/uluckyxh/openmoss/wordpress-skill)<a href="https://agentmods.dev/skills/uluckyxh/openmoss/wordpress-skill"><img src="https://agentmods.dev/badge/skills/uluckyxh/openmoss/wordpress-skill.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.01785 |
| Opus 5 | $0.00015 | $0.00892 |
| Sonnet 5 | $0.00006 | $0.00357 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
wordpress-skill 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Skill
你可以使用 wordpress-cli.py 工具来管理 WordPress 站点。该工具位于本 Skill 目录下。
站点信息
- 站点地址：
https://www.1m-reviews.com - 工具路径：
wordpress-cli.py
可用命令
文章管理（post）
# 列出文章
post list # 列出文章（默认 10 篇）
post list --status draft # 按状态筛选: publish/draft/pending/private
post list --categories 3 # 按分类 ID 筛选
post list --search "关键词" # 搜索文章
post list --order asc --orderby date # 排序: asc/desc，字段: date/id/title/modified
post list --after "2026-03-01T00:00:00" # 仅返回此时间之后发布的文章
post list --before "2026-03-06T00:00:00" # 仅返回此时间之前发布的文章
post list --author 1 # 按作者 ID 筛选
post list --page 2 --per-page 20 # 分页
# 获取单篇文章
post get <id> # 查看文章详情
post get <id> --edit # 编辑模式（含原始正文内容）
# 创建文章（默认状态: draft）
post create "文章标题" # 创建草稿
post create "标题" --content "<p>正文 HTML</p>" # 指定正文
post create "标题" --content-file article.html # 从文件读取正文
post create "标题" --status publish # 直接发布: draft/publish/pending/private
post create "标题" --categories 3,5 # 分类 ID，逗号分隔
post create "标题" --tags 1,2 # 标签 ID，逗号分隔
post create "标题" --slug "my-article" # URL Slug
post create "标题" --excerpt "摘要" # 文章摘要
post create "标题" --featured-media 8 # 特色图媒体 ID
post create "标题" --format standard # 格式: standard/aside/gallery/link/image/quote/video/audio
post create "标题" --comment-status closed # 评论: open/closed
post create "标题" --ping-status closed # Pingback: open/closed
post create "标题" --sticky # 置顶文章
# 更新文章
post update <id> --title "新标题"
post update <id> --content "<p>新正文</p>"
post update <id> --status publish # 草稿改为发布
post update <id> --categories 3 --tags 1,2
post update <id> --slug "new-slug"
post update <id> --featured-media 10
# 删除文章
post delete <id> # 移至回收站
post delete <id> --force # 跳过回收站直接删除
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 205 lines · 29 tokens per session scan A 4ba4d57e86a2
wordpress-skill is a skill published in the GitHub repository uluckyXH/OpenMOSS (1,318 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,785 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…