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 nicojunk/claude-ig --skill ig-strategygit clone --depth 1 https://github.com/nicojunk/claude-igWrote 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/nicojunk/claude-ig/ig-strategy)<a href="https://agentmods.dev/skills/nicojunk/claude-ig/ig-strategy"><img src="https://agentmods.dev/badge/skills/nicojunk/claude-ig/ig-strategy/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/nicojunk/claude-ig/ig-strategy"><img src="https://agentmods.dev/badge/skills/nicojunk/claude-ig/ig-strategy.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.00043 | $0.01625 |
| Opus 5.5 | $0.00017 | $0.00650 |
| Sonnet 5.5 | $0.00009 | $0.00325 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
ig-strategy 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 2mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IG Strategy -- Content strategy and positioning analysis
Key references:
references/account-baseline.md-- current metrics, content mix, audience datareferences/competitor-framework.md-- competitor landscape, positioning mapreferences/content-rules.md-- brand voice, content pillars, banned topics
Phase 1: Account Analysis
Pull live data to establish the current state:
- Account info:
get_user_infofor follower count, bio, media count. - Recent media:
get_user_mediafor last 30-50 posts. - Post insights:
get_post_insightsfor reach, saves, shares per post. - Account insights:
get_user_insightsfor follower demographics, reach trends, activity times.
Calculate from the data:
- Average engagement rate (overall and by format)
- Save rate trend (increasing, stable, declining)
- Reach-to-follower ratio trend
- Content type distribution (actual vs baseline targets)
- Posting frequency and consistency score
Load references/account-baseline.md for comparison with historical data.
RULE: All strategic recommendations must be grounded in actual data. Never make recommendations based on assumptions about performance.
Phase 2: Audience Mapping
Build an audience profile from available data and niche knowledge:
Demographics (from API insights if available)
- Age distribution
- Gender split
- Top locations (cities/countries)
- Active hours and days
Psychographics (from content performance patterns)
- What topics get the highest save rate? (indicates what the audience values)
- What topics get the highest share rate? (indicates what they identify with)
- What gets the most comments? (indicates what they have opinions on)
- What gets ignored? (indicates misalignment)
Audience Segments
Define 2-4 audience segments based on the data:
| Segment | Description | Content Preference | Engagement Style |
|---|---|---|---|
| [Name] | [who they are] | [what they want] | [how they interact] |
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.
- 2mo ago First seen · 203 lines · 43 tokens per session scan A dcf84e85b0cb
ig-strategy is a skill published in the GitHub repository nicojunk/claude-ig (23 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,625 once invoked, about $0.0002 per session on Opus 5.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-30.
ig-strategy compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ig-strategynicojunk/claude-ig | Skill | 23 | 2mo ago | MIT | A | 43 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |