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/huifer/claude-code-seo/content-strategygit clone --depth 1 https://github.com/huifer/claude-code-seoWrote 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/commands/huifer/claude-code-seo/content-strategy)<a href="https://agentmods.dev/commands/huifer/claude-code-seo/content-strategy"><img src="https://agentmods.dev/badge/commands/huifer/claude-code-seo/content-strategy.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.00005 | $0.00327 |
| Opus 5 | $0.00003 | $0.00163 |
| Sonnet 5 | $0.00001 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
content-strategy 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.
What it actually says
分析项目的内容策略，提供全面的建议。识别内容空白、建议支柱页面主题、分析集群内容机会、评估内容发布频率、提供内容日历建议、检查关键词蚕食问题。
功能
- ✅ 识别内容空白和机会
- ✅ 建议支柱页面主题
- ✅ 分析集群内容机会
- ✅ 评估内容发布频率
- ✅ 提供内容日历建议
- ✅ 检查关键词蚕食问题
参数
--deep-analysis: 执行深度分析（包括竞争对手内容对比）
使用示例
示例 1：基本分析
/content-strategy
输出内容策略分析和建议，包括：
- 内容统计和现状
- 识别的内容空白（按优先级）
- 支柱页面建议
- 集群内容机会
- 发布时间表建议
示例 2：深度分析
/content-strategy --deep-analysis
包含额外的：
- 竞争对手内容对比
- 内容差距分析
- 更详细的支柱页面大纲
- 季节性内容机会
相关命令
/pillar-pages- 支柱页面详细分析/topic-clusters- 集群内容分析/ee-audit- E-E-A-T 审计
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 · 53 lines · 5 tokens per session scan A 30252e44cb6d
content-strategy is a command published in the GitHub repository huifer/claude-code-seo (110 stars, last pushed 8mo ago), licensed MIT. It adds 5 tokens to every session and 327 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.