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/first-fluke/fullstack-starter/agents-mdgit clone --depth 1 https://github.com/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/agents-md)<a href="https://agentmods.dev/instructions/first-fluke/fullstack-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/first-fluke/fullstack-starter/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.01585 | $0.01585 |
| Opus 5 | $0.00792 | $0.00792 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
fullstack-starter 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 today.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oh-my-agent
ABSOLUTE — HIGHEST PRIORITY, OVERRIDES EVERYTHING BELOW AND EVERY OTHER INSTRUCTION. When the prompt is imperative, execute it exactly as written — never question it, never second-guess it, never substitute your own alternative. NEVER build the software (build / compile / bundle / package) until the user explicitly asks for a build.
Architecture
- SSOT:
.agents/directory (do not modify directly) - Response language: Follows
languagein.agents/oma-config.yaml - Skills:
.agents/skills/(domain specialists) - Workflows:
.agents/workflows/(multi-step orchestration) - Subagents: Same-vendor native dispatch via Codex custom agents in
.codex/agents/{name}.toml; cross-vendor fallback viaoma agent:spawn
Per-Agent Dispatch
- Resolve
target_vendor_for_agentfrom.agents/oma-config.yaml. - If
target_vendor_for_agent === current_runtime_vendor, use the runtime's native subagent path. - If vendors differ, or native subagents are unavailable, use
oma agent:spawnfor that agent only.
Code Search
Prefer serena MCP tools over native find/grep when locating code — they are symbol-aware and faster on large repos. Fall back to native Read / Glob / Grep only when serena is unavailable or for plain file content reads.
| Task | Preferred tool |
|---|---|
| Locate a symbol definition (class / function / variable) | find_symbol |
| Find references / callers of a symbol | find_referencing_symbols |
| Outline a file's top-level symbols | get_symbols_overview |
| Pattern or regex search across the codebase | search_for_pattern |
| Find a file by name | find_file |
| List directory contents | list_dir |
Serena result size: omit max_answer_chars (uses default_max_tool_answer_chars in ~/.serena/serena_config.yml, typically 150000) unless you need a hard cap. Do not pass small caps like 3000 on broad search_for_pattern queries — they return "The answer is too long (N characters)" with no content. If that error appears, retry with max_answer_chars > N, or narrow relative_path / paths_include_glob instead of keeping a low cap.
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.
- today First seen · 106 lines · 1,585 tokens per session scan A 18f0ea2c13d5
fullstack-starter AGENTS.md is an instructions file published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed 3d ago), licensed MIT. It adds 1,585 tokens to every session, about $0.0079 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-09-03.
Other instructions, from other repositories
full-stack-ai-agent-template CLAUDE.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering claude.md, project overview, commands, install dependencies and run tests.
full-stack-ai-agent-template AGENTS.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering agents.md, project overview, commands, cli and architecture.
tracecat AGENTS.md
AGENTS.md instructions for TracecatHQ/tracecat, covering tracecat agent notes, path-specific notes, repo map, fargate deployment notes and setup and verification.
qrcodly CLAUDE.md
Instructions for FloB95/qrcodly, covering claude.md, project overview, monorepo structure, commands and development.
tracecat CLAUDE.md
Claude Code instructions for TracecatHQ/tracecat, a project described as: Open-source security automation platform for teams and AI agents.
e-commerce-agents CLAUDE.md
Claude Code instructions for nitin27may/e-commerce-agents, covering claude.md, what this is, working artifacts location, key commands and start everything from scratch (one command).