Borrowing it
Nothing to install: this file belongs to webjsdev/webjs. 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/webjsdev/webjs/main/.claude/skills/webjs-instagram-post/SKILL.mdgit clone --depth 1 https://github.com/webjsdev/webjsWrote 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/webjsdev/webjs/webjs-instagram-post)<a href="https://agentmods.dev/skills/webjsdev/webjs/webjs-instagram-post"><img src="https://agentmods.dev/badge/skills/webjsdev/webjs/webjs-instagram-post/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/webjsdev/webjs/webjs-instagram-post"><img src="https://agentmods.dev/badge/skills/webjsdev/webjs/webjs-instagram-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 11 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 29 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 159 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 223 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00116 | $0.02933 |
| Opus 5.5 | $0.00046 | $0.01173 |
| Sonnet 5.5 | $0.00023 | $0.00587 |
| Haiku 4.5 | $0.00012 | $0.00293 |
Grade A, and why
webjs-instagram-post 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.
allowed-tools: Bash(curl:*), Bash(magick:*), Bash(convert:*), Bash(identify:*), Bash(cp:*), Bash(mkdir:*), Bash(ls:*), Bash(git:*), Read, Write How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post to Instagram for SEO
Every Instagram post on the WebJs account exists for SEO reach, not for personal updates. So each post carries two things you build here: a freshly created branded image, and a keyword-rich caption that names the capability and links back to a webjs.dev page. Never publish a plain-text post and never reuse a stale image.
Account and API
- Account is the
@webjs_devprofessional (BUSINESS) account. - Numeric user id is
17841441038146182. Ongraph.instagram.comyou can also address it asme. - API flavor is the Instagram API with Instagram Login, so every call goes
to
https://graph.instagram.com/v25.0/...with a long-lived USER access token. An app token (theappid|secretshape) can never post.
Credentials (never printed, never committed)
The token lives in a gitignored file OUTSIDE the repo:
~/.config/webjs/instagram.env
with IG_TOKEN, IG_USER_ID, and IG_APP_SECRET. Source it inside a script
and reference ${IG_TOKEN}. NEVER cat, echo, or otherwise print the file,
and NEVER copy the token into the repo, a commit, or a chat message. If the
file is missing, ask the user to generate a long-lived user token from the
Meta dashboard and place it there.
set -a; . ~/.config/webjs/instagram.env; set +a
Step 1: create the branded SEO image (required, JPEG)
The Instagram publishing API accepts a JPEG only, pulled from a public URL.
build-post.sh renders at 2x supersample and outputs a sharpened 1440x1440
JPEG (quality 95) by default. This matters: a flat 1080 render looks soft in
Instagram's DESKTOP full-size view on a high-DPI screen after IG re-compresses
it, and the supersampled 1440 stays crisp. Do not drop back to a 1x 1080 render.
Match the webjs.dev OG theme, which is a NEAR-BLACK card with a soft warm glow
in the top-right corner, the orange squircle mark plus the white webjs
wordmark, a bold white headline with ONE orange-highlighted phrase, gray
subtext, and a small-caps footer meta row with a webjs.dev URL. It is a dark
card with orange accents, NOT an orange background.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 239 lines · 116 tokens per session scan A d99136818b7c
webjs-instagram-post is a skill published in the GitHub repository webjsdev/webjs (27 stars, last pushed 13d ago), licensed MIT. It adds 116 tokens to every session and 2,933 once invoked, about $0.0005 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-30.
Other skills, from other repositories
hono-core
Hono ultrafast web framework fundamentals - routing, context, handlers, and response patterns for multi-runtime deployment.
htmx-alpine-frontend
Build a no-build-step interactive frontend with HTMX partial swaps and Alpine.js state, served from CDN over server-rendered Jinja pages.
bun
Bun all-in-one JavaScript runtime and toolkit reference. Covers runtime APIs (file I/O, HTTP server, SQLite, shell), ultra-fast package manager, built-in bundler with plugins, test runner with mocking, TypeScript support, and Node.js compatibility.
Node.js Debugger
Use this skill when debugging runtime failures in Node.js or Bun: stack traces, async errors, startup crashes, port conflicts, and memory leaks.
Bun Patterns
Use this skill when working in Bun-based projects (or Node projects running on Bun) and you want reliable runtime expectations, dependency management, and debugging workflows.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.