Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/pinkpixel-dev/skills-collection-1/apify-audience-analysis)<a href="https://agentmods.dev/skills/pinkpixel-dev/skills-collection-1/apify-audience-analysis"><img src="https://agentmods.dev/badge/skills/pinkpixel-dev/skills-collection-1/apify-audience-analysis/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/pinkpixel-dev/skills-collection-1/apify-audience-analysis"><img src="https://agentmods.dev/badge/skills/pinkpixel-dev/skills-collection-1/apify-audience-analysis.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.01164 |
| Opus 5 | $0.00015 | $0.00582 |
| Sonnet 5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
apify-audience-analysis 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
100% identical to apify-audience-analysis — 0 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audience Analysis
Analyze and understand your audience using Apify Actors to extract follower demographics, engagement patterns, and behavior data from multiple platforms.
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 audience analysis type (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analysis script
- [ ] Step 5: Summarize findings
Step 1: Identify Audience Analysis Type
Select the appropriate Actor based on analysis needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Facebook follower demographics | apify/facebook-followers-following-scraper |
FB followers/following lists |
| Facebook engagement behavior | apify/facebook-likes-scraper |
FB post likes analysis |
| Facebook video audience | apify/facebook-reels-scraper |
FB Reels viewers |
| Facebook comment analysis | apify/facebook-comments-scraper |
FB post/video comments |
| Facebook content engagement | apify/facebook-posts-scraper |
FB post engagement metrics |
| Instagram audience sizing | apify/instagram-profile-scraper |
IG profile demographics |
| Instagram location-based | apify/instagram-search-scraper |
IG geo-tagged audience |
| Instagram tagged network | apify/instagram-tagged-scraper |
IG tag network analysis |
| Instagram comprehensive | apify/instagram-scraper |
Full IG audience data |
| Instagram API-based | apify/instagram-api-scraper |
IG API access |
| Instagram follower counts | apify/instagram-followers-count-scraper |
IG follower tracking |
| Instagram comment export | apify/export-instagram-comments-posts |
IG comment bulk export |
| Instagram comment analysis | apify/instagram-comment-scraper |
IG comment sentiment |
| YouTube viewer feedback | streamers/youtube-comments-scraper |
YT comment analysis |
| YouTube channel audience | streamers/youtube-channel-scraper |
YT channel subscribers |
| TikTok follower demographics | clockworks/tiktok-followers-scraper |
TT follower lists |
| TikTok profile analysis | clockworks/tiktok-profile-scraper |
TT profile demographics |
| TikTok comment analysis | clockworks/tiktok-comments-scraper |
TT comment engagement |
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 · 123 lines · 30 tokens per session scan A dcbbe7a848c3
apify-audience-analysis is a skill published in the GitHub repository pinkpixel-dev/skills-collection-1 (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,164 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to apify-audience-analysis, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
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…