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/photon-hq/cli/agents-mdgit clone --depth 1 https://github.com/photon-hq/cliWhat 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.00712 | $0.00712 |
| Opus 5 | $0.00356 | $0.00356 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
cli 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 2d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide for @photon-ai/cli
Mission
You're updating this CLI in response to upstream API changes in @photon-ai/dashboard-api. The API type contract arrives as a version bump of that dependency (in package.json/bun.lock). Your job: make bun run check pass.
Hard Rules (CI will fail if violated)
- Use Bun exclusively — never Node, npm, pnpm, yarn
- Never hand-edit API types — they come from the
@photon-ai/dashboard-apidependency; update them by bumping its version - Never add forbidden dependencies: axios, chalk, zod, jest, vitest, ts-node, ws, express, dotenv, ioredis, pg, better-sqlite3
- Every command must use
getApi()from~/lib/api.ts+ Eden treaty pattern — never rawfetch() - Destructure Eden responses as
{ data, error, status }— check error before using data - Handle 401 by throwing
SessionExpiredError(caught centrally inhandleTopLevelError) - Never delete or rewrite snapshot files without justification in PR body under "## Snapshot changes"
- One PR = one upstream version bump — don't bundle refactors
- Never modify files in
.github/workflows/orscripts/agent-flow/
Soft Rules (reviewer will flag)
- Match the style in
src/commands/projects.ts: same option ordering (--api-host, -t/--token, --json), same error handling - New DTOs go in
src/lib/types.ts, cast at the API boundary - Prefer adding fields to existing DTOs over creating parallel types
- All user-facing output uses
c.dim(),c.success(),c.error()from~/lib/output.ts - Comments only when intent isn't obvious from the code
Anti-patterns (we've seen AI do these — don't)
- Splitting the
ProjectDTO into one type per command - Adding try/catch around every
getApi()call (handled centrally insrc/index.ts#handleTopLevelError) - Using
console.log(JSON.stringify(...))instead of the output helpers - Replacing
picocolorswithchalk - Using
node:fsinstead ofBun.file - Adding
dotenv(Bun auto-loads .env) - Importing from
@elysiajs/edendirectly instead of usinggetApi()
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.
- 2d ago First seen · 48 lines · 712 tokens per session scan A 6cfd63587d6d
cli AGENTS.md is an instructions file published in the GitHub repository photon-hq/cli (296 stars, last pushed 23d ago), licensed MIT. It adds 712 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
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).
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.
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).
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.
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.