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 agentproto/ts --skill instagramgit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/instagram)<a href="https://agentmods.dev/skills/agentproto/ts/instagram"><img src="https://agentmods.dev/badge/skills/agentproto/ts/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/agentproto/ts/instagram"><img src="https://agentmods.dev/badge/skills/agentproto/ts/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.00049 | $0.01357 |
| Opus 5.5 | $0.00020 | $0.00543 |
| Sonnet 5.5 | $0.00010 | $0.00271 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
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 1mo 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.
const r = await fetch(path, { How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instagram — recon plan (web private API)
✅ Instagram adapter —
SOCIAL_PLATFORMS.instagramin@agstudio/browser-social(sites/instagram/adapter.ts): profile · authored · connection (followers/following) · engagement-received (commenters — the only IG edge; likers 403), as aSocialSourcePort. In-pageigFetch(x-ig-app-id + x-csrftoken) + re-focus drift defense. Graph ingest:scripts/profile.ts instagram <username> --graph-only→ registry capture →landFootprintgraph sink (platform"instagram"): profile→SocialPerson, posts→AUTHORED, commenters→COMMENTED, followers/following→FOLLOWS. Same domain as LinkedIn → cross-platform queries just work. Likers stay 403.
✅ Validated live (logged in, read-only): headers
x-ig-app-id:936619743392459
x-csrftoken(csrftoken) +x-requested-with:XMLHttpRequest.web_profile_info?username=→200 (pk, full_name, follower/post counts).feed/user/<pk>/?count=N→200 (media: code, pk, like_count, comment_count, caption).media/<pk>/comments/→200 (commenters: @username + user pk + text = engagement edge). ⚠️media/<pk>/likers/→403 (IG hides likers). IG graph = followers/following + commenters, not likers. web_profile_info media edges are empty → usefeed/user/<pk>/.
Internal API: web private REST https://www.instagram.com/api/v1/... +
GraphQL https://www.instagram.com/graphql/query (and /api/graphql) using
doc_id. The web UI calls these directly.
Auth (from the page)
- cookies (
sessionid,csrftoken,ds_user_id) ride same-origin. - headers required:
x-ig-app-id: 936619743392459(the web app id — stable; also in the page's shared-data / a request header, capture to confirm),x-csrftoken: <csrftoken cookie>,x-requested-with: XMLHttpRequest,x-asbd-id(a small constant in requests — capture),x-ig-www-claim(echoed from a prior response headerx-ig-set-www-claim).
In-page fetch:
async path => {
const csrf = (document.cookie.match(/csrftoken=([^;]+)/) || [])[1]
const r = await fetch(path, {
headers: {
"x-ig-app-id": "936619743392459",
"x-csrftoken": csrf,
"x-requested-with": "XMLHttpRequest",
},
})
return await r.json()
}
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.
- 1mo ago First seen · 109 lines · 49 tokens per session scan A f664a8ecbb17
instagram is a skill published in the GitHub repository agentproto/ts (10 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,357 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
demo-recorder
Use when the user wants a scripted screen-recording demo video of a web app, a narration script or text-to-speech voice-over for one, or a dubbed cut.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
browser-tools
Safety rules over the upstream agent-browser skill (scraping ethics, auth, request pacing, local URLs). URL policy is the Claude Code sandbox's job when the operator enables it. Use for browser automation.
qa-screenshot
Screenshot a page (deploy preview or a dev server on localhost) in the sandbox's headless Chromium, look at it, and embed it in a task comment. Use to verify a visual change or record before/after evidence.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).