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/guest-blogsgit 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/guest-blogs)<a href="https://agentmods.dev/commands/huifer/claude-code-seo/guest-blogs"><img src="https://agentmods.dev/badge/commands/huifer/claude-code-seo/guest-blogs.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.00006 | $0.03992 |
| Opus 5 | $0.00003 | $0.01996 |
| Sonnet 5 | $0.00001 | $0.00798 |
| Haiku 4.5 | $0.00001 | $0.00399 |
Grade A, and why
guest-blogs 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 5d 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 — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.
基于项目内容分析，提供客座博客机会和投稿策略。生成 Google 搜索语法、列出高质量资源网站、提供质量评估标准和投稿建议。
功能
- ✅ 自动分析项目主题和关键词
- ✅ 生成 Google 高级搜索语法
- ✅ 列出客座博客资源（从 resources/guest-blog-sources.md 读取）
- ✅ 提供质量评估标准
- ✅ 生成投稿邮件模板（使用 --template）
- ✅ 提供个性化投稿建议
参数
-
--niche <topic>: 指定细分领域（可选）- 如果不提供，自动分析项目内容
- 示例：
--niche "plumbing",--niche "web development"
-
--template: 生成投稿邮件模板（可选标志）- 包含初次联系邮件和内容提案邮件
- 从 templates/guest-blog-pitch.md 读取
使用示例
示例 1：自动分析项目
/guest-blogs
输出：
# 客座博客机会分析
## 项目内容分析
基于对项目内容的分析，识别出以下主题和关键词：
### 主要话题
1. **话题 1：管道维修**
- 关键词：plumbing repair, emergency plumbing, pipe maintenance
- 相关文章：8 篇
- 受众兴趣：高
2. **话题 2：家庭维护**
- 关键词：home maintenance, DIY plumbing, household tips
- 相关文章：5 篇
- 受众兴趣：中高
3. **话题 3：管道服务**
- 关键词：plumbing services, local plumber, professional plumbing
- 相关文章：4 篇
- 受众兴趣：高
### 目标受众
- **人群特征**：房主、物业经理、DIY 爱好者
- **地理位置**：旧金山湾区
- **主要需求**：紧急维修、预防性维护、成本估算
---
## Google 搜索策略
### 立即可用的搜索语法
**话题 1：管道维修**
```bash
# 基础客座博客搜索
"plumbing repair" "write for us"
"emergency plumbing" "guest post"
"pipe maintenance" "become a contributor"
# 网站限定搜索
site:medium.com "plumbing" "write for us"
site:wordpress.com "plumbing" "guest post"
# URL 搜索
inurl:write-for-us "plumbing"
inurl:guest-post "emergency plumbing"
# 教育机构
site:.edu "plumbing" "write for us"
site:.edu "home maintenance" "guest post"
# 行业特定
site:homes.com "plumbing" "contributor"
site:realtor.com "home maintenance" "write for us"
# 高级组合
("plumbing repair" OR "emergency plumbing") AND ("write for us" OR "guest post")
"plumbing" "write for us" -sponsored -paid -"payment required"
"plumbing" intitle:"write for us" inurl:blog
话题 2：家庭维护
"home maintenance" "write for us"
"DIY plumbing" "guest post"
"household tips" "become a contributor"
site:medium.com "home maintenance" "write for us"
话题 3：管道服务
"plumbing services" "write for us"
"local plumber" "guest post"
"professional plumbing" "become a contributor"
地理位置搜索
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.
- 5d ago First seen · 575 lines · 0 tokens per session scan A 1cda0a975676
guest-blogs is a command published in the GitHub repository huifer/claude-code-seo (110 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 3,992 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.