Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vivy-yi/awesome-skillsnpx agentmods add skills/vivy-yi/awesome-skills/blog-collectorWrote 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/vivy-yi/awesome-skills/blog-collector)<a href="https://agentmods.dev/skills/vivy-yi/awesome-skills/blog-collector"><img src="https://agentmods.dev/badge/skills/vivy-yi/awesome-skills/blog-collector/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/vivy-yi/awesome-skills/blog-collector"><img src="https://agentmods.dev/badge/skills/vivy-yi/awesome-skills/blog-collector.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.00104 | $0.01048 |
| Opus 5 | $0.00052 | $0.00524 |
| Sonnet 5 | $0.00021 | $0.00210 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
blog-collector 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 "https://r.jina.ai/https://mp.weixin.qq.com/s/xxxxx" How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Collector
Collects blog articles from various platforms and saves them to the blogs/ directory.
Workflow
1. Receive Article URL
echo "Article URL to collect:"
# User provides: https://mp.weixin.qq.com/s/xxxxx
2. Extract Content
For WeChat Articles:
# Option A: Browser extraction (recommended for WeChat)
openclaw browser open targetUrl:"https://mp.weixin.qq.com/s/xxxxx"
# Then snapshot to get content, scroll to load all images
# Option B: Jina Reader
curl -s "https://r.jina.ai/https://mp.weixin.qq.com/s/xxxxx"
For Other Platforms:
# Zhihu
curl -s "https://r.jina.ai/https://zhihu.com/xxxxx"
# Medium
curl -s "https://r.jina.ai/https://medium.com/xxxxx"
# 掘金
curl -s "https://r.jina.ai/https://juejin.cn/xxxxx"
3. Extract and Download Images
# After getting content, extract image URLs via browser JS:
openclaw browser act targetId:<tab_id> request:'{"kind": "evaluate", "fn": "(() => { return Array.from(document.querySelectorAll(\"img\")).filter(img => img.src && img.src.includes(\"mmbiz\")).map(img => ({src: img.src, alt: img.alt || \"\", width: img.naturalWidth})).slice(0, 20); })()"}'
# Download images (filter imgIndex=0 = logo)
mkdir -p blogs/images/YYYY-MM-DD-article-slug/
curl -s -L -o "blogs/images/YYYY-MM-DD-article-slug/cover.jpg" "<cover_url>"
4. Generate Markdown
cat > "blogs/YYYY-MM-DD-article-slug.md" << 'EOF'
# Article Title
> **作者**：Author Name | **来源**：Source Name | **发布日期**：YYYY-MM-DD
> **原文**：https://original-url.com
---
---
## 文章正文
[Content here...]
## 参考资料
- [原文链接](https://original-url.com)
EOF
5. Determine Article Type & Destination
| Type | Destination |
|---|---|
| 论文/学术 | papers/ |
| 技术博客 | blogs/ |
| 行业分析 | blogs/analysis/ |
| 工具介绍 | blogs/ |
6. Push to GitHub
cd /Volumes/waku/github-维护/awesome/awesome-skills-repos
git add blogs/
git add blogs/images/
git commit -m "Add: <article title> (YYYY-MM-DD)"
git push
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.
- 12d ago First seen · 133 lines · 0 tokens per session scan A 25175676d597
blog-collector is a skill published in the GitHub repository vivy-yi/awesome-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 104 tokens to every session and 1,048 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…