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/rahmanef63/control-room/agents-mdgit clone --depth 1 https://github.com/rahmanef63/control-roomWhat 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.00099 | $0.00099 |
| Opus 5 | $0.00049 | $0.00049 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
control-room 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.
What it actually says
VPS Control Room — Agent Instructions
The single source of truth for every coding agent (Claude, Codex, Gemini) is CLAUDE.md in the repo root. Read it before starting any task.
This file is an intentional pointer — three near-identical instruction copies were collapsed into one to avoid drift. Runtime is HTTP-only (frontend → agent HTTP API → host); there is no Convex layer on the hot path.
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 · 9 lines · 99 tokens per session scan A 00fb04e91533
control-room AGENTS.md is an instructions file published in the GitHub repository rahmanef63/control-room (19 stars, last pushed 3d ago), licensed MIT. It adds 99 tokens to every session, about $0.0005 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
serverless-full-stack-webapp-starter-kit AGENTS.md
AGENTS.md instructions for aws-samples/serverless-full-stack-webapp-starter-kit, covering agents.md, commands, install all dependencies, webapp and cdk.
data-table-filters CLAUDE.md
Instructions for openstatusHQ/data-table-filters, covering claude.md, project overview, monorepo structure (pnpm + turborepo), key commands and database.
karakeep CLAUDE.md
Claude Code instructions for karakeep-app/karakeep, a project described as: A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search.
Codex-Skills AGENTS.md
Instructions for TheGoat395/Codex-Skills, covering repository operating notes, required checks, evidence rules and change hygiene.
souls-directory CLAUDE.md
Instructions for thedaviddias/souls-directory, covering claude.md — project context for ai assistants, project overview, tech stack, critical rules and database is convex.
agentgram CLAUDE.md
Instructions for agentgram/agentgram, covering claude.md — agentgram development guide, project overview, tech stack, monorepo structure and core architecture patterns.