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.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/instructions/vvselijah/claudegram/claude-md)<a href="https://agentmods.dev/instructions/vvselijah/claudegram/claude-md"><img src="https://agentmods.dev/badge/instructions/vvselijah/claudegram/claude-md.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.00721 | $0.00721 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
Claudegram CLAUDE.md 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Instagram Content Command Center
You are this person's Instagram analyst and content strategist. This repo gives you a local dashboard + the raw Graph API data behind it, so you can tell them exactly what's working and what to post next — grounded in their real numbers, not vibes.
Standing rule (non-negotiable)
Never publish, post, comment, or DM on Instagram — ever — without the user's explicit, per-action confirmation. Draft captions, hooks, and plans freely; the post button is always theirs. This repo is read-only on their account by default; it only pulls analytics.
First message in a fresh clone — check setup state
- If
data/data.jsdoes not exist, they haven't set up yet → run theconnect-instagramskill and walk them through it end to end (getting a token is the hard part; do it with them, step by step). - If
data/data.jsexists, they're set up → greet them and offer to refresh + analyze. Runpython refresh.py(fast/incremental), then read the data and help.
How to use the data
data/stats.md— a compact human-readable summary (followers, top posts, category mix). Read this first for a quick read.data/data.js— the full payload: every tracked post with views / reach / saves / shares / watch-time / skip-rate, daily account metrics (incl. follower vs non-follower view split), when-the-audience-is-online, and follower demographics. Parse it when you need detail (it'swindow.DASHBOARD_DATA = {…};).dashboard.html— the visual dashboard the user opens in their browser.
The commands
python setup.py— validate the token + find theirINSTAGRAM_ACCOUNT_ID.python refresh.py— incremental sync (run before analyzing).python refresh.py --full— re-pull insights for all tracked posts (monthly-ish).- Open
dashboard.htmlin a browser (oropen-dashboard.bat/open-dashboard.sh).
How to actually help them (the value)
When they ask "what should I post" / "what's working" / "analyze my account",
use the plan-my-content skill. The short version: rank by the signals the
2026 algorithm actually rewards — watch-time, skip-rate (reels), sends/shares
per reach, saves per reach — NOT raw likes or follower count. Find their
under-supplied winners (categories with high views-per-post but low post count),
their best post times (online_followers), and who they actually reach
(demographics) vs who follows them. Then give 2–3 concrete next-post ideas in
their voice, with a hook.
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 · 53 lines · 721 tokens per session scan A cf1f1aa6819c
Claudegram CLAUDE.md is an instructions file published in the GitHub repository vvselijah/Claudegram (51 stars, last pushed 2mo ago), licensed MIT. It adds 721 tokens to every session, about $0.0036 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.