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-captionnpx skills add nicojunk/claude-ig --skill ig-captiongit 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-caption)<a href="https://agentmods.dev/skills/nicojunk/claude-ig/ig-caption"><img src="https://agentmods.dev/badge/skills/nicojunk/claude-ig/ig-caption.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.00100 | $0.01923 |
| Opus 5 | $0.00050 | $0.00962 |
| Sonnet 5 | $0.00020 | $0.00385 |
| Haiku 4.5 | $0.00010 | $0.00192 |
Grade A, and why
ig-caption 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IG Caption: Optimized Instagram Captions
Writes complete, paste-ready Instagram captions. Every caption follows a proven structure optimized for saves and DM-sends (the two highest-value algorithm signals in 2026). Captions sound like the creator wrote them. Never robotic, never filler.
Load account context (niche, audience, voice, language) from references/account-baseline.md.
If not configured, ask the user about their niche, audience, and voice.
Key references:
references/content-rules.md— Caption structure, CTA hierarchy, hashtag strategyreferences/scoring-system.md— Caption & CTA sub-criteria (20pts max)references/account-baseline.md— Proven caption patterns from top-performing posts
Workflow
Phase 1: Context
Gather the inputs needed to write a targeted caption.
- Identify post type — Reel, Carousel, Feed image, or Story highlight
- Identify topic — The specific content theme (e.g., "16:8 Fehler", "Proteinmythen", "Krafttraining ab 40")
- Identify visual hook — The text overlay or visual hook used on the post itself (needed to create a thematically linked but different caption opener)
- If any of these are missing, ask the user once. Do not proceed without all three.
Phase 2: Caption Structure
Load references/content-rules.md and apply the proven caption structure.
- Read content-rules.md for current caption structure rules, CTA hierarchy, and hashtag strategy
- Read account-baseline.md to identify which caption patterns performed best on recent top posts
- Map the structure for this specific post:
- Hook variation opener (thematically linked to visual hook, never identical)
- Value body (problem statement, insight, or actionable tip)
- Line break separator
- CTA (selected from hierarchy based on post type and goal)
- Hashtag set (3-5 niche-specific)
Phase 3: Writing
Write the complete caption in German following these rules.
3a. Hook Variation Opener
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 · 199 lines · 100 tokens per session scan A 2b7e81eccff7
ig-caption is a skill published in the GitHub repository nicojunk/claude-ig (11 stars, last pushed 6mo ago), licensed MIT. It adds 100 tokens to every session and 1,923 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-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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…