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 skills add Livus-AI/Skills-MCP --skill content-researchgit clone --depth 1 https://github.com/Livus-AI/Skills-MCPWrote 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/livus-ai/skills-mcp/content-research)<a href="https://agentmods.dev/skills/livus-ai/skills-mcp/content-research"><img src="https://agentmods.dev/badge/skills/livus-ai/skills-mcp/content-research/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/livus-ai/skills-mcp/content-research"><img src="https://agentmods.dev/badge/skills/livus-ai/skills-mcp/content-research.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.00050 | $0.00539 |
| Opus 5 | $0.00025 | $0.00269 |
| Sonnet 5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
content-research 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 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.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Research Skill
Gather and synthesize raw information on a single topic into a structured brief that serves as the foundation for multi-platform content creation.
Workflow
- Receive topic from user or identify trending topic in niche
- Research using web search, news, and authoritative sources
- Synthesize findings into the Research Brief format
- Output structured brief for downstream content generation
Research Goals
When researching a topic, focus on:
- 3-5 significant recent developments - What's new and noteworthy?
- 1-2 surprising statistics - Data that challenges assumptions or creates shock value
- Core narrative - What's the bigger story or trend?
- Key players - Companies, tools, or people driving the change
- Actionable takeaway - One clear action the audience can take
Output Format
Always structure the research brief as follows:
## Research Brief: [Topic]
**Core Narrative:** [1-2 sentence summary of the main story or trend]
**Key Developments:**
1. [Development 1]: [Brief description with source]
2. [Development 2]: [Brief description with source]
3. [Development 3]: [Brief description with source]
**Surprising Data:**
- [Statistic]: [Context and source link]
**Key Players:**
- [Company/Tool/Person 1]
- [Company/Tool/Person 2]
**Actionable Takeaway:** [Single, clear action someone can take]
**Sources:**
- [Source 1 URL]
- [Source 2 URL]
Quality Checklist
Before completing the research brief, verify:
- All claims have credible sources
- Statistics are recent (within last 6 months preferred)
- Core narrative is clear and compelling
- Takeaway is specific and actionable
- Brief is concise (under 500 words)
Next Steps
After completing the research brief, proceed to:
twitter-thread-generator- Convert brief into Twitter threadlinkedin-post-adapter- Adapt for LinkedIn audiencenewsletter-expander- Expand into full newsletter issue
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 · 75 lines · 50 tokens per session scan A 86ed8ebb4837
content-research is a skill published in the GitHub repository Livus-AI/Skills-MCP (2 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 539 once invoked, about $0.0003 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-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…