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 instructions/nanmicoder/open-image-prompts/agents-mdgit clone --depth 1 https://github.com/NanmiCoder/open-image-promptsWrote 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/nanmicoder/open-image-prompts/agents-md)<a href="https://agentmods.dev/instructions/nanmicoder/open-image-prompts/agents-md"><img src="https://agentmods.dev/badge/instructions/nanmicoder/open-image-prompts/agents-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 | $0.01323 | $0.01323 |
| Opus 5 | $0.00661 | $0.00661 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
open-image-prompts AGENTS.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 4d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for coding agents working in or starting up this repository.
What this repository is
An open, local-first visual prompt archive plus two installable Agent Skills. The application is a read-only SQLite API (Python, standard library only) behind a React/Vite frontend. Nothing here trains, labels, or writes prompt data.
Get it running
Prerequisites: Node.js 20.19+ or 22.12+, and Git. Python arrives via uv, which
start.sh installs into .oip/tools/ if it is missing.
./start.sh # macOS/Linux; Windows: start.bat
start.sh is the whole setup: it prepares Python, downloads the dataset,
installs frontend packages, and starts the API and frontend together. Open the
URL it prints, not a URL you assumed — see "Ports" below.
To skip the ~4 GB of image packs (the gallery then falls back to each record's original source URL):
OIP_FETCH_SKIP_IMAGES=1 ./start.sh
Step-by-step instead of the launcher:
uv sync --locked
npm run data:pull # or data:pull:db to skip image packs
npm --prefix web ci
npm run dev
The dataset is not in Git
A clone gives you code, Skills, taxonomy, and small indexes — not the corpus.
db/prompts.db.gz (~80 MB) and images/ (~4.2 GB across nine monthly packs)
are downloaded from GitHub Releases by scripts/fetch_dataset.py, which verifies
every asset's sha256 against data/dataset-manifest.json. Both paths are
gitignored, and re-running the fetch is safe: verified assets are skipped.
Expect this layout after a full pull:
db/prompts.db.gz # compressed archive from Releases
images/<tweet_id>/N.jpg # extracted image packs
.oip/runtime/prompts.db # expanded read-only SQLite, created on first start
.oip/packs/*.sha256 # extraction markers so unchanged packs are skipped
Search and retrieval work without the image packs. Only local image preview needs them.
Ports
Nothing binds a predictable port unconditionally, so never hardcode one.
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.
- 4d ago First seen · 136 lines · 1,323 tokens per session scan A 424342b75abe
open-image-prompts AGENTS.md is an instructions file published in the GitHub repository NanmiCoder/open-image-prompts (232 stars, last pushed 4d ago), licensed MIT. It adds 1,323 tokens to every session, about $0.0066 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.