Borrowing it
Nothing to install: this file belongs to vvselijah/Claudegram. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vvselijah/Claudegram/main/.claude/skills/connect-instagram/SKILL.mdgit clone --depth 1 https://github.com/vvselijah/ClaudegramWrote 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/vvselijah/claudegram/connect-instagram)<a href="https://agentmods.dev/skills/vvselijah/claudegram/connect-instagram"><img src="https://agentmods.dev/badge/skills/vvselijah/claudegram/connect-instagram/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/vvselijah/claudegram/connect-instagram"><img src="https://agentmods.dev/badge/skills/vvselijah/claudegram/connect-instagram.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.00086 | $0.01463 |
| Opus 5 | $0.00043 | $0.00732 |
| Sonnet 5 | $0.00017 | $0.00293 |
| Haiku 4.5 | $0.00009 | $0.00146 |
Grade A, and why
connect-instagram scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
python -c "import urllib.request,urllib.parse,json,sys; a=urllib.parse.urlencode({'grant_type':'fb_exchange_token','client_id':sys.argv[1],'client_secret':sys.argv[2],'fb_exchange_token':sys.argv[3]}); print(json.load(ur 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.
Connect Instagram (setup walkthrough)
Your job: get this person from zero to a working dashboard. Getting the token is
the only hard part — do it WITH them, one step at a time, and verify each step
before moving on. Some steps only they can do (clicking inside Meta's UI / the
Instagram app); do those parts as clear, numbered instructions and wait for them
to confirm. The steps you can run (the token exchange, setup.py, refresh.py),
run yourself.
Never ask them to paste a token into a file. Tokens and the app secret are used transiently and live only in environment variables.
Step 1 — Make the Instagram account eligible (user does this in the IG app)
Tell them to confirm all three:
- Their Instagram is a Professional account (Business or Creator) — IG app → Settings → Account type and tools → Switch to professional account.
- It's linked to a Facebook Page they admin — IG app → Settings → linked accounts / "Connect a Facebook Page". (Create a Page if they don't have one; it can be empty.)
- They can log into that Facebook account on a computer. Wait for "done" before continuing. (Insights require Business/Creator + a linked Page.)
Step 2 — Create a Meta app (user does this at developers.facebook.com)
Guide them:
- Go to developers.facebook.com → log in → My Apps → Create App.
- Use case: choose "Other" → app type "Business" → name it anything → create.
- In the app dashboard, Add Product → Instagram → Graph API (a.k.a. "Instagram" / "Instagram Graph API"). Also add Facebook Login if prompted.
- From App settings → Basic, have them copy the App ID and App Secret (the secret is revealed with their password). They'll paste both to you in Step 4 — you'll use them once and never store them.
Step 3 — Generate a short-lived token (user does this in Graph API Explorer)
- Go to developers.facebook.com/tools/explorer.
- Top right: select their app in the "Meta App" dropdown, and "User Token".
- Click Add a Permission and add ALL of these:
instagram_basic,instagram_manage_insights,pages_show_list,pages_read_engagement. - Click Generate Access Token → approve the popup (select their Page + IG account).
- Copy the token it shows. This one is short-lived (expires in ~1 hour) — that's expected; Step 4 turns it into a 60-day one. Have them paste it to you.
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.
- 10d ago First seen · 105 lines · 86 tokens per session scan A bf217be4eb17
connect-instagram is a skill published in the GitHub repository vvselijah/Claudegram (51 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 1,463 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…