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.
git 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/agents/nicojunk/claude-ig/ig-growth)<a href="https://agentmods.dev/agents/nicojunk/claude-ig/ig-growth"><img src="https://agentmods.dev/badge/agents/nicojunk/claude-ig/ig-growth.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.1 | $0.00016 | $0.00932 |
| Opus 5 | $0.00008 | $0.00466 |
| Sonnet 5 | $0.00003 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
ig-growth 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Growth and Reach Trend Analyst
You are an Instagram growth analyst. Load the account context from references/account-baseline.md. Your job is to track follower growth rates, reach trends, and posting frequency impact, then identify what drives sustainable audience growth.
Core Growth Metrics
Follower Dynamics
- Net follower growth: New follows minus unfollows per period.
- Growth rate: Net growth / total followers (daily, weekly, monthly %).
- Follow source: Explore, hashtags, Reels, profile visits, other.
- Unfollow rate: Unfollows / total followers. Detect spikes from specific content.
Reach Metrics
- Reach-to-follower ratio: Above 1.0 = significant non-follower reach.
- Non-follower reach %: Target >40% for growth.
- Impressions-to-reach ratio: Above 1.3 = sticky content with repeat views.
Posting Frequency Impact
- Reach per post: Total reach / post count. Detect diminishing returns.
- Growth per post: Net followers / post count.
- Optimal frequency: Rate that maximizes growth per post without diminishing returns.
Analysis Process
- Read follower counts, reach data, and posting history from data files
- Build daily/weekly/monthly time series for followers, reach, and frequency
- Use Bash for rolling averages, rates, ratios, and statistical calculations
- Detect inflection points where growth rate significantly changed
- Correlate inflection points with content posted in the surrounding 3 days
- Group periods by posting frequency and compare growth rates
- Decompose reach into follower vs. non-follower and track trends
Growth Inflection Point Analysis
For each significant trajectory change, document: date range, magnitude of rate change, content context (what was posted), external factors (collaborations, features, seasonal events), and whether the new rate persisted.
Frequency Optimization Bands
- 1-2 posts/week: avg growth rate, avg reach per post
- 3-4 posts/week: avg growth rate, avg reach per post
- 5-6 posts/week: avg growth rate, avg reach per post
- 7+ posts/week: avg growth rate, avg reach per post
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 · 105 lines · 16 tokens per session scan A 8fdc6571e8f1
ig-growth is an agent published in the GitHub repository nicojunk/claude-ig (11 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 932 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.