Borrowing it
Nothing to install: this file belongs to Ampli-Group/agentic-mobile-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Ampli-Group/agentic-mobile-blueprint/main/AGENTS.mdgit clone --depth 1 https://github.com/Ampli-Group/agentic-mobile-blueprintWrote 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/ampli-group/agentic-mobile-blueprint/agents-md)<a href="https://agentmods.dev/instructions/ampli-group/agentic-mobile-blueprint/agents-md"><img src="https://agentmods.dev/badge/instructions/ampli-group/agentic-mobile-blueprint/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.1 | $0.01721 | $0.01721 |
| Opus 5 | $0.00860 | $0.00860 |
| Sonnet 5 | $0.00344 | $0.00344 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
agentic-mobile-blueprint AGENTS.md scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **Edge functions** | `curl` the endpoint or check `supabase functions logs`. Read the terminal running `mise run supabase:function` for errors. | How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Context
This document helps LLM agents understand the codebase structure, environment, and available tooling.
For coding patterns and conventions, see the skills in .agents/skills/.
Task Workflow
Every task must be verified, not just coded. Follow this workflow:
1. Check Environment
Before writing any code, confirm the relevant services are running:
- Run
supabase statusfrom the project root to check Supabase (DB, auth, storage, edge runtime) - List terminal files (
lsthe terminals folder) and read them to find running processes - If services are down, start them with the appropriate
mise runcommand and keep the terminal open
Reading logs: Each mise run command runs in a terminal whose output is captured in a text file. To read logs:
- List the terminals folder to see all active terminals
- Read the terminal file (or its tail) to see live output, errors, and stack traces
- After making changes, re-read the same terminal file to check for new errors or successful recompilation
This gives you three verification channels for every change:
- Terminal logs — compile errors, runtime errors, request logs
- Browser MCP — visual state of frontend and Supabase Studio
- Maestro MCP — visual state of the mobile app on the simulator
2. Implement
Write the code changes. Use the skills in .agents/skills/ for coding patterns.
3. Verify
After every change, verify it works using the appropriate tools:
| Layer | How to verify |
|---|---|
| Edge functions | curl the endpoint or check supabase functions logs. Read the terminal running mise run supabase:function for errors. |
| Frontend | Read the terminal running mise run frontend for compile errors. Use browser_navigate + browser_snapshot to visually confirm. Check browser_console_messages for runtime errors. |
| Mobile | Test on both platforms: start iOS (mise run mobile:ios) and Android (mise run mobile:android). Read their terminal output for Metro/Expo errors. Use Maestro MCP (list_devices, take_screenshot, inspect_view_hierarchy, tap/navigate as needed) on each device to visually confirm the UI on both. |
| Database | Use browser_navigate to Supabase Studio (get port from supabase status) and verify tables/data with browser_snapshot. Or run SQL via supabase db query. |
| Cross-layer | Verify each layer touched. E.g. new API + mobile screen = check edge function logs + take mobile screenshot. |
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.
- 7d ago First seen · 137 lines · 1,721 tokens per session scan A 47c6efd66fb9
agentic-mobile-blueprint AGENTS.md is an instructions file published in the GitHub repository Ampli-Group/agentic-mobile-blueprint (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,721 tokens to every session, about $0.0086 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
mcp-react-native-toolkit copilot-instructions.md
Copilot instructions for ItamiForge/mcp-react-native-toolkit, covering github copilot (vs code) instructions, project context, core rules, api validation and best practices.
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
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).