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/rm2thaddeus/pixel_detective/agents-mdgit clone --depth 1 https://github.com/rm2thaddeus/Pixel_DetectiveWhat 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.03292 | $0.03292 |
| Opus 5 | $0.01646 | $0.01646 |
| Sonnet 5 | $0.00658 | $0.00658 |
| Haiku 4.5 | $0.00329 | $0.00329 |
Grade A, and why
Pixel_Detective 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 3d 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines - Pixel Detective Project
🎯 Overview
This document provides comprehensive guidelines for AI agents working on the Pixel Detective project, which consists of two production-ready applications:
- Pixel Detective - AI-powered media search engine
- Dev Graph - Temporal knowledge graph for code evolution
Key Principle: This entire codebase was built through AI-assisted development. Every change should maintain this philosophy and code quality standards.
📋 Quick Navigation Guide
This root-level AGENTS.md serves as a navigation hub. For detailed development guidelines, consult the appropriate subdirectory documentation:
🎨 Pixel Detective (Media Search)
When working on: Media search, image ingestion, CLIP/BLIP models, vector search, UMAP visualization
Primary Documentation:
backend/AGENTS.md- Backend service development (Ingestion, ML Inference, GPU-UMAP)frontend/AGENTS.md- Frontend development (Next.js, React, Chakra UI)backend/ARCHITECTURE.md- Backend system designfrontend/ARCHITECTURE.md- Frontend architecture
Quick Reference:
- Backend services: 3 FastAPI microservices (ports 8001, 8002, 8003)
- Frontend: Next.js 14 with App Router (port 3000)
- Database: Qdrant vector database (port 6333)
- AI Models: CLIP (embeddings), BLIP (captions), RAPIDS cuML (UMAP)
🗺️ Dev Graph (Code Knowledge Graph)
When working on: Git history ingestion, knowledge graph, Neo4j, code symbol extraction, relationship derivation
Primary Documentation:
developer_graph/AGENTS.md- Dev Graph module developmentdeveloper_graph/architecture.md- System architecture and data modeldeveloper_graph/routes/AGENTS.md- API route handlersdev_graph_audit/AGENTS.md- Data quality and auditing
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.
- 3d ago First seen · 367 lines · 3,292 tokens per session scan A 3ee5c0d9733f
Pixel_Detective AGENTS.md is an instructions file published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 7mo ago), licensed MIT. It adds 3,292 tokens to every session, about $0.0165 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.