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 STELIORD/agentic-awesome-skills/plugin install agentic-awesome-skillsWrote 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/steliord/agentic-awesome-skills/apify-content-analytics)<a href="https://agentmods.dev/skills/steliord/agentic-awesome-skills/apify-content-analytics"><img src="https://agentmods.dev/badge/skills/steliord/agentic-awesome-skills/apify-content-analytics/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/steliord/agentic-awesome-skills/apify-content-analytics"><img src="https://agentmods.dev/badge/skills/steliord/agentic-awesome-skills/apify-content-analytics.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.00030 | $0.01221 |
| Opus 5 | $0.00015 | $0.00611 |
| Sonnet 5 | $0.00006 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
apify-content-analytics 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 7d 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.
This is a copy
97% identical to apify-content-analytics — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Analytics
Track and analyze content performance using Apify Actors to extract engagement metrics from multiple platforms.
When to Use
- You need engagement, growth, or ROI metrics for posts, reels, videos, ads, or hashtags.
- The task is to use Apify Actors to collect cross-platform content performance data.
- You need exported analytics results and a concise interpretation of what content is performing best.
Prerequisites
(No need to check it upfront)
.envfile withAPIFY_TOKEN- Node.js 20.6+ (for native
--env-filesupport) mcpcCLI tool:npm install -g @apify/mcpc
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify content analytics type (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analytics script
- [ ] Step 5: Summarize findings
Step 1: Identify Content Analytics Type
Select the appropriate Actor based on analytics needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Post engagement metrics | apify/instagram-post-scraper |
Post performance |
| Reel performance | apify/instagram-reel-scraper |
Reel analytics |
| Follower growth tracking | apify/instagram-followers-count-scraper |
Growth metrics |
| Comment engagement | apify/instagram-comment-scraper |
Comment analysis |
| Hashtag performance | apify/instagram-hashtag-scraper |
Branded hashtags |
| Mention tracking | apify/instagram-tagged-scraper |
Tag tracking |
| Comprehensive metrics | apify/instagram-scraper |
Full data |
| API-based analytics | apify/instagram-api-scraper |
API access |
| Facebook post performance | apify/facebook-posts-scraper |
Post metrics |
| Reaction analysis | apify/facebook-likes-scraper |
Engagement types |
| Facebook Reels metrics | apify/facebook-reels-scraper |
Reels performance |
| Ad performance tracking | apify/facebook-ads-scraper |
Ad analytics |
| Facebook comment analysis | apify/facebook-comments-scraper |
Comment engagement |
| Page performance audit | apify/facebook-pages-scraper |
Page metrics |
| YouTube video metrics | streamers/youtube-scraper |
Video performance |
| YouTube Shorts analytics | streamers/youtube-shorts-scraper |
Shorts performance |
| TikTok content metrics | clockworks/tiktok-scraper |
TikTok analytics |
What ships with it
1 file 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.
- 7d ago First seen · 132 lines · 30 tokens per session scan A 587582a8e19a
apify-content-analytics is a skill published in the GitHub repository STELIORD/agentic-awesome-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,221 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to apify-content-analytics, differing in 3 lines, and is treated as a copy.
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…
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
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…