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/noahduongmaster/vibe-code-stack-for-ceos/agents-mdgit clone --depth 1 https://github.com/NoahDuongMaster/vibe-code-stack-for-ceosWhat 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.07954 | $0.07954 |
| Opus 5 | $0.03977 | $0.03977 |
| Sonnet 5 | $0.01591 | $0.01591 |
| Haiku 4.5 | $0.00795 | $0.00795 |
Grade A, and why
vibe-code-stack-for-ceos 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 — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Vibe Code Stack For CEOs
AI-first Turborepo monorepo (pnpm 11, Node 22, TypeScript strict): 3 frontend apps + 3 backend services + 3 shared packages, deployed to Cloudflare and private AWS EC2 infrastructure.
- This file is the single source of truth for agent behavior.
CLAUDE.mdis a symlink to it — always editAGENTS.md. - This is intentionally the ONLY
AGENTS.mdin the repo (no nested per-workspace files) — rules are scoped per workspace inside this file to avoid drift. Don't create nested agent files. - When a rule here conflicts with existing code, follow the rule and flag the code.
Monorepo map
| Workspace | Package | What it is | Deploys to |
|---|---|---|---|
apps/dapp |
@apps/dapp |
Next.js 16 App Router (vinext/Vite) | Cloudflare Workers |
apps/admin |
@apps/admin |
React 19 SPA (Rsbuild + React Router, no RSC) | Cloudflare Pages |
apps/landing |
@apps/landing |
Astro static site (zero JS by default) | Cloudflare Workers |
services/trading-rpc |
@services/trading-rpc |
NestJS host on Fastify: Connect for edge + native Nest gRPC for Node services | AWS EC2 (Docker/ECR/SSM) |
services/admin-rpc |
@services/admin-rpc |
Admin-facing NestJS RPC facade; calls trading-rpc over native gRPC for coin data | AWS EC2 (Docker/ECR/SSM) |
services/api-gateway |
@services/api-gateway |
Edge gateway Worker (Hono: request-id, CORS, self-hosted Durable Object rate-limit, opt-in JWT auth, upstream proxy) | Cloudflare Workers |
packages/protocol |
@packages/protocol |
Protobuf schemas, buf codegen → src/gen/ |
— |
packages/api-core |
@packages/api-core |
Shared RPC impl + CORS-aware fetch handler | — |
packages/api-client |
@packages/api-client |
Typed Connect-RPC browser client | — |
Rule scope: Server/Client Component rules apply to apps/dapp only. All three
frontend apps use an FSD-inspired layered architecture with explicit
bootstrap/screens names and framework-specific entrypoints documented below.
The backend slice architecture applies to packages/api-core + services/*
(see Architecture rules).
Everything else (naming, testing, git, security) applies repo-wide.
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 · 622 lines · 7,954 tokens per session scan A 692d97e5a430
vibe-code-stack-for-ceos AGENTS.md is an instructions file published in the GitHub repository NoahDuongMaster/vibe-code-stack-for-ceos (126 stars, last pushed 9d ago), licensed MIT. It adds 7,954 tokens to every session, about $0.0398 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
cladding CLAUDE.md
Instructions for qwerfunch/cladding, covering maintainer guide for ai-assisted work on cladding, spec authoring — always hash, never f-nnn, version bumps — use the script, detector additions — count is auto-recomputed and plugin manifest mirrors — built, not hand-authored.
cladding AGENTS.md
Instructions for qwerfunch/cladding, covering agents.md, 1. project, 2. setup, 3. verify before pushing and 4. code & comment style.
intelligence-sync CLAUDE.md
Instructions for ainova-systems/intelligence-sync, covering claude.md, archive status, final layout and contract and validation.
ai-first-toolkit AGENTS.md
Instructions for techwolf-ai/ai-first-toolkit, covering techwolf ai-first toolkit, repository purpose, working conventions and codex install notes.
next-payload-ai-fluent-starter CLAUDE.md
Claude Code instructions for joshuamartyn/next-payload-ai-fluent-starter, covering read me first, 🔒 critical rule (must follow), 🧰 mcp servers & roles, 📦 task contract (keep work small & shippable) and 🧭 standard work session (do this every time).
next-payload-ai-fluent-starter AGENTS.md
AGENTS.md instructions for joshuamartyn/next-payload-ai-fluent-starter, covering task-driven development with github + archon, 🔒 critical rule, 📦 task management rules (github), 📚 research workflow (archon) and research checklist (before coding).