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 agentmods add skills/moses607/socialforge/channel-competitor-analysisnpx skills add moses607/socialforge --skill channel-competitor-analysisgit clone --depth 1 https://github.com/moses607/socialforgeWrote 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/moses607/socialforge/channel-competitor-analysis)<a href="https://agentmods.dev/skills/moses607/socialforge/channel-competitor-analysis"><img src="https://agentmods.dev/badge/skills/moses607/socialforge/channel-competitor-analysis.svg" alt="Measured on agentmods" 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 | $0.00100 | $0.00826 |
| Opus 5 | $0.00050 | $0.00413 |
| Sonnet 5 | $0.00020 | $0.00165 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
channel-competitor-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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channel & Competitor Analysis
Growth leaves fingerprints. Every channel that works is running a repeatable system — a few pillars, a hook style, a format, a cadence — and you can read it off their public output. The goal is not to copy; it's to find the pattern they're exploiting and the gap they're leaving open for you.
Inputs
Ask for (or work with what's given): the profile/handle, 5-20 of their recent posts (ideally their top performers), and follower/engagement numbers if available. If you only have a URL, work from titles, hooks, thumbnails, and visible metrics.
Method
- Separate outliers from baseline. Rank their posts by engagement relative to their own average. The 2-3× outliers are the signal — that's what the audience actually wants. The baseline is filler.
- Decode the outliers on five axes:
- Hook — the opening move and archetype (see
hook-machine). - Format — talking-head, listicle, story, tutorial, reaction, B-roll+VO.
- Pillar — the recurring topic/theme it belongs to.
- Emotion — what it makes the viewer feel (status, fear, curiosity, belonging, aspiration).
- Structure — hook → escalation → payoff → CTA; where retention is engineered.
- Hook — the opening move and archetype (see
- Map the pillars. Cluster all posts into 3-5 content pillars; note the % of output and % of total engagement per pillar. The high-engagement/low-output pillar is an underexploited vein.
- Read the cadence & funnel. Posting frequency, best-performing times, and how they convert attention (link in bio, series, lead magnet, product).
- Find the weaknesses (your opening). Where are they weak or absent? Common gaps: no strong hooks, no series/retention loop, ignoring a platform, weak CTA, a pillar their audience loves but they underserve, poor production, or a tone that alienates a sub-segment.
Output template
## Analysis: <channel/creator>
Baseline vs outliers: avg engagement <x>; outliers <list top 3 + their multiple>
### What's working (their winning system)
Pillars (share of output / share of engagement): <table>
Hook style: <..> | Dominant format: <..> | Core emotion: <..>
Cadence & best times: <..> | Conversion path: <..>
### Why the outliers hit
<per top post: hook + structure + emotion, 1-2 lines each>
### Their weaknesses = your openings
<3-5 specific, exploitable gaps>
### Attack plan for you
<3 concrete content moves that use their gap + your edge>
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 First seen · 55 lines · 100 tokens per session scan A 70fbd5f8bd45
channel-competitor-analysis is a skill published in the GitHub repository moses607/socialforge (2 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 826 once invoked, about $0.0005 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
blog-notebooklm
Query Google NotebookLM notebooks for source-grounded, citation-backed answers from user-uploaded documents. Manages notebook library, handles Google authentication, and supports smart discovery. Works standalone via /blog notebooklm or internally from blog-write and blog-researcher for source-grounded research…
blog-schema
Generate complete JSON-LD schema markup for blog posts with Article/BlogPosting, Person, Organization, BreadcrumbList, ImageObject, and optional FAQPage. Validates against Google requirements and warns about deprecated types. Use when user says "schema", "blog schema", "json-ld", "structured data", "schema markup"…
self-media-content-delivery
将自媒体创作里程碑保存成文件，管理版本、核验路径、生成完整发布包并更新内容索引。用于保存平台第一版完整成稿、多平台合集、短视频脚本、分镜、定稿、发布包和复盘报告，或用户说“保存一下、整理交付、归档、生成发布清单”时。标题微调、删一句和临时候选不单独保存新版本。.
self-media-trend-radar
安全追踪热点、研究关键词和拆解竞品内容，并将结果转成原创选题和证据包。用于用户要求找热点、看趋势、分析爆款、研究竞品账号、拆标题或开头、比较内容结构、发现评论需求和判断时效窗口。只做公开信息研究和只读采集，不自动互动、发布或使用主账号登录态抓取竞品。.
short-drama
制作多集 AI 微短剧：建立剧集圣经和角色参考，完成分集剧本、逐镜 I2V、对白审计、配音字幕 BGM 与成片，保持跨镜跨集一致性。 当用户说“AI/横屏/竖屏/微短剧、拍短剧、分集剧本、连续剧情视频、做几集短剧”时使用。 单条非剧情视频用 auto-short-video；只写单条脚本用 video-script；只生成一个视频片段用 ai-video-gen。.
multi-voice-dubbing
多角色对话配音：按 cast 和逐行对白为不同角色分配音色与情绪，合成多声线音轨和带角色名字幕。 当用户说“多角色/双人/剧本/对话配音、多人对白、不同角色不同声音、有声剧配音”时使用。 单一公共音色用 tts-voiceover；克隆本人音色用 voice-clone；整部短剧制作由 short-drama 编排。.