Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add signalcompose/claude-tools/plugin install x-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/skills/signalcompose/claude-tools/x-articles-knowledge)<a href="https://agentmods.dev/skills/signalcompose/claude-tools/x-articles-knowledge"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/x-articles-knowledge/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/skills/signalcompose/claude-tools/x-articles-knowledge"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/x-articles-knowledge.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.00092 | $0.00554 |
| Opus 5.5 | $0.00037 | $0.00222 |
| Sonnet 5.5 | $0.00018 | $0.00111 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade A, and why
x-articles-knowledge 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.
What it actually says
X Articles ナレッジベース
X (Twitter) Articles への記事投稿に関する知見をまとめたリファレンス集。
用途別リファレンス
ヘッダー画像を生成したい場合
${CLAUDE_PLUGIN_ROOT}/skills/x-articles-knowledge/references/header-image.md を読む。
スクリプト: python3 ${CLAUDE_PLUGIN_ROOT}/scripts/header-image.py --title "..." --subtitle "..."
記事のドラフトを作成したい場合
${CLAUDE_PLUGIN_ROOT}/skills/x-articles-knowledge/references/article-structure.md を読む。
記事の方針・構成テンプレート・X Articles の制約（マークダウン変換ルール）を確認すること。
エディタにコンテンツを貼り付けたい場合
${CLAUDE_PLUGIN_ROOT}/skills/x-articles-knowledge/references/draftjs-editor.md を読む。
DraftJS の制約、成功パターン（DataTransfer + ClipboardEvent）、カーソル操作の注意点。
ファクトチェック・レビューをしたい場合
${CLAUDE_PLUGIN_ROOT}/skills/x-articles-knowledge/references/fact-checking.md を読む。
URL 確認方法、コマンド名・マーケットプレイス名の検証手順。
ブラウザ自動操作をしたい場合
${CLAUDE_PLUGIN_ROOT}/skills/x-articles-knowledge/references/browser-automation.md を読む。
Claude in Chrome MCP / Playwright MCP の使い分け、フォールバック手順。
コマンドとの連携
| コマンド | 参照先 |
|---|---|
/x-article:draft |
article-structure.md |
/x-article:header |
header-image.md（スクリプト直接実行） |
/x-article:review |
fact-checking.md |
/x-article:publish |
draftjs-editor.md + browser-automation.md |
What ships with it
5 files 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.
- 1mo ago First seen · 55 lines · 92 tokens per session scan A 31613fff8e1e
x-articles-knowledge is a skill published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 554 once invoked, about $0.0004 per session on Opus 5.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.
Other skills, from other repositories
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…
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…
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…