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/79e/auto-openai-account/agents-mdgit clone --depth 1 https://github.com/79E/auto-openai-accountWrote 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/79e/auto-openai-account/agents-md)<a href="https://agentmods.dev/instructions/79e/auto-openai-account/agents-md"><img src="https://agentmods.dev/badge/instructions/79e/auto-openai-account/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.00995 | $0.00995 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
auto-openai-account 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 5d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Summary
auto-openai-account is a Go backend with an embedded React UI for local account automation workflows.
Production should run as one Go service that serves:
/api/*JSON API and SSE events/React app/assets/*React static assets
The backend stays in Go. The frontend stays in React, TypeScript, Vite, and Tailwind CSS. SQLite is the first storage backend.
Read First
Before making non-trivial changes, read these files:
docs/requirements.mdfor product scope and first-version requirementsdocs/architecture.mdfor module layout and boundariesdocs/design.mdfor UI and interaction directiondocs/api.mdfor current API contracts
Project Layout
apps/server/main.go: Go server entrypointapps/web: React + Vite frontendinternal/api: HTTP routing, request parsing, response formatting, SSE endpoint handlersinternal/domain: shared business types, JSON fields, status constants, default settingsinternal/storage: SQLite schema, migrations, persistence queries, data mappinginternal/runner: job creation, concurrency, cancellation, runtime logs, SSE fanoutinternal/legacy: account automation implementation kept behind current app boundariesinternal/proxypool: proxy connectivity testsinternal/webui: embedded frontend filesystem and static UI handlerdocs: product, architecture, API, and design notes
Development Commands
Backend:
go test ./...
go run ./apps/server
Frontend:
cd apps/web
npm run dev
npm run build
The default server listen address is :8080. It can be overridden with AUTO_OPENAI_ACCOUNT_LISTEN.
Verification Rules
Run the smallest useful verification for the files changed.
- Backend changes:
go test ./... - Frontend changes:
cd apps/web && npm run build - API contract changes: update
docs/api.mdand verify frontend types inapps/web/src/types.ts - UI behavior changes: verify the affected page builds and follows
docs/design.md
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.
- 5d ago First seen · 119 lines · 995 tokens per session scan A 8c085087ab25
auto-openai-account AGENTS.md is an instructions file published in the GitHub repository 79E/auto-openai-account (51 stars, last pushed 3mo ago), licensed MIT. It adds 995 tokens to every session, about $0.0050 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.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-release stance: foundation over blast radius, repository layout, commands and host sandbox failures.