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/nicojunk/claude-ig/ig-commentnpx skills add nicojunk/claude-ig --skill ig-commentgit 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-comment)<a href="https://agentmods.dev/skills/nicojunk/claude-ig/ig-comment"><img src="https://agentmods.dev/badge/skills/nicojunk/claude-ig/ig-comment.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.00039 | $0.01570 |
| Opus 5 | $0.00019 | $0.00785 |
| Sonnet 5 | $0.00008 | $0.00314 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
ig-comment 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 6d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IG Comment -- Comment response strategy and automation
Key references:
references/comment-responder.md-- Make.com automation blueprint, webhook setup, response templatesreferences/account-baseline.md-- current response rate, average response time
Phase 1: Strategy Overview
Why Comments Matter
- Instagram rewards accounts that generate conversations (comments + replies)
- Every reply is a signal to the algorithm that the post is worth distributing
- Unanswered questions reduce future engagement (followers stop commenting)
- Comments are the top source of DM conversations (and conversions)
Response Rate Target
- Target: Respond to 30-40% of all comments within 2 hours
- Priority: Questions and high-intent comments get 100% response rate
- Minimum: Never let a question go unanswered for more than 24 hours
What NOT to Respond To
- Single-emoji comments (heart, fire, clap) -- like them, do not reply
- Bot/spam comments -- delete and block
- Promotional comments from other accounts -- delete
- Comments with only tags (@friend) -- the tag IS the engagement, no reply needed
Phase 2: Voice Rules
All comment responses must sound like the creator wrote them. This is non-negotiable.
Load the creator's voice profile from references/account-baseline.md.
Tone
- Warm, direct, encouraging
- Use "du" always (never "Sie")
- Short and punchy (under 50 words per reply)
- Use 1-2 emojis max per reply (favorites: heart, sparkle, muscle)
- Never sound like a support agent or chatbot
Language Patterns
- Start with: name mention, affirmation, or direct answer
- Avoid: "Danke fuer dein Feedback", "Toll, dass du das ansprichst", or any template-sounding phrase
- Use: casual spoken German, contractions, exclamation marks for enthusiasm
Examples (Good)
- "Jaaa mega! Probier mal die Variante mit Haferflocken, das macht nochmal satter"
- "Oh das kenn ich so gut. Schreib mir mal per DM, ich schick dir was dazu"
- "Haha genau DAS. Die meisten unterschaetzen wie wichtig das ist"
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.
- 6d ago First seen · 183 lines · 39 tokens per session scan A 9ea751922b36
ig-comment is a skill published in the GitHub repository nicojunk/claude-ig (11 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,570 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-08-30.
Other skills, from other repositories
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…