AAS Core is a local control plane for coding agents that lets them search a large catalogue of skills, choose a stack, validate it, and create a reproducible plan. It is used to assemble and review agent workflows through its CLI, local MCP server, catalogue, plugins, and Workbench. The catalogue add-ons provide the skills, plugins, bundles, and workflows that AAS Core helps agents select and validate.
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 sickn33/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/sickn33/agentic-awesome-skills/apify-trend-analysis)<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/apify-trend-analysis"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/apify-trend-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/sickn33/agentic-awesome-skills/apify-trend-analysis"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/apify-trend-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.01230 |
| Opus 5 | $0.00015 | $0.00615 |
| Sonnet 5 | $0.00006 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
apify-trend-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 3d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- apify-trend-analysis — 100% identical, 1 lines differ
- apify-trend-analysis — 100% identical, 1 lines differ
- apify-trend-analysis — 97% identical, 3 lines differ
- apify-trend-analysis — 97% identical, 3 lines differ
- apify-trend-analysis — 97% identical, 3 lines differ
- apify-trend-analysis — 97% identical, 3 lines differ
- apify-trend-analysis — 97% identical, 3 lines differ
- apify-trend-analysis — 92% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trend Analysis
Discover and track emerging trends using Apify Actors to extract 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 trend 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 Trend Type
Select the appropriate Actor based on research needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Search trends | apify/google-trends-scraper |
Google Trends data |
| Hashtag tracking | apify/instagram-hashtag-scraper |
Hashtag content |
| Hashtag metrics | apify/instagram-hashtag-stats |
Performance stats |
| Visual trends | apify/instagram-post-scraper |
Post analysis |
| Trending discovery | apify/instagram-search-scraper |
Search trends |
| Comprehensive tracking | apify/instagram-scraper |
Full data |
| API-based trends | apify/instagram-api-scraper |
API access |
| Engagement trends | apify/export-instagram-comments-posts |
Comment tracking |
| Product trends | apify/facebook-marketplace-scraper |
Marketplace data |
| Visual analysis | apify/facebook-photos-scraper |
Photo trends |
| Community trends | apify/facebook-groups-scraper |
Group monitoring |
| YouTube Shorts | streamers/youtube-shorts-scraper |
Short-form trends |
| YouTube hashtags | streamers/youtube-video-scraper-by-hashtag |
Hashtag videos |
| TikTok hashtags | clockworks/tiktok-hashtag-scraper |
Hashtag content |
| Trending sounds | clockworks/tiktok-sound-scraper |
Audio trends |
| TikTok ads | clockworks/tiktok-ads-scraper |
Ad trends |
| Discover page | clockworks/tiktok-discover-scraper |
Discover trends |
| Explore trends | clockworks/tiktok-explore-scraper |
Explore content |
| Trending content | clockworks/tiktok-trends-scraper |
Viral content |
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.
- 3d ago Changed · +1 lines ef8a16eb446c
- 6d ago First seen · 134 lines · 30 tokens per session scan A c1035acc4410
apify-trend-analysis is a skill published in the GitHub repository sickn33/agentic-awesome-skills (46,230 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,230 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
build-nitro-modules
Builds React Native Nitro Modules from scratch in a monorepo. Scaffolds with Nitrogen, authors HybridObject TypeScript specs, generates native boilerplate, implements in C++/Swift/Kotlin, wires an example app, and prepares for npm publishing. Use when creating a new Nitro Module, implementing native functionality via…
laravel-api
Build production-ready RESTful APIs with Laravel. Covers authentication (Sanctum/Passport), versioning, resources, rate limiting, and API testing.
wordpress-developer
Develop professional WordPress sites, custom themes, and plugins. Covers WordPress best practices, hooks system, custom post types, WP REST API, and security.
redis-master
Leverage Redis for caching, sessions, pub/sub, queues, rate limiting, and real-time features. Design Redis data structures for optimal performance.
mysql-expert
Design, optimize, and maintain MySQL databases. Covers schema design, indexing strategies, query optimization, replication, and performance tuning.
e2e-automator
Build robust end-to-end test suites with Playwright or Cypress. Covers page objects, fixtures, visual testing, and CI integration.