Borrowing it
Nothing to install: this file belongs to az-coder-123/firebase-cloud-messenger. 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/az-coder-123/firebase-cloud-messenger/main/AGENTS.mdgit clone --depth 1 https://github.com/az-coder-123/firebase-cloud-messengerWrote 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/az-coder-123/firebase-cloud-messenger/agents-md)<a href="https://agentmods.dev/instructions/az-coder-123/firebase-cloud-messenger/agents-md"><img src="https://agentmods.dev/badge/instructions/az-coder-123/firebase-cloud-messenger/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/az-coder-123/firebase-cloud-messenger/agents-md"><img src="https://agentmods.dev/badge/instructions/az-coder-123/firebase-cloud-messenger/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00407 | $0.00407 |
| Opus 5.5 | $0.00163 | $0.00163 |
| Sonnet 5.5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
firebase-cloud-messenger 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 1mo 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.
What it actually says
AGENTS.md
Overview
This document outlines the guidelines and best practices for developing AI Agents within the Flutter application designed for desktop platforms (Windows, MacOS, and Linux). It is essential that all agents adhere to these principles to ensure maintainability, clarity, and efficiency in the codebase.
Development Guidelines
1. Code Clarity and Maintainability
- Clean Code Principles: All source code must be clear, understandable, and maintainable. Follow the Clean Code principles to enhance readability and reduce complexity.
- Single Responsibility Principle: Each file, class, and method/function should have a single responsibility. This minimizes code duplication and logic duplication, promoting high reusability.
2. State Management
- Riverpod: Utilize Riverpod for state management within the application. Ensure that state management is efficient and follows best practices to maintain application performance.
3. Library Usage
- Stable Libraries: Use libraries that are stable, trusted, and actively maintained. Avoid using libraries that are deprecated or no longer supported.
4. Avoid Deprecated Code
- No Deprecated Classes/Methods: Ensure that no deprecated classes, methods, or functions are used in the codebase. Regularly check for updates and replacements for deprecated features.
5. Code Analysis
- Run Flutter Analyze: Always run
flutter analyzeafter completing any task (creating/updating code, fixing bugs, etc.) to ensure there are no compile/build errors. This step is crucial for maintaining code quality.
6. Documentation
- English Documentation: All documentation must be written in English. It should be clear, professional, and closely aligned with real-world practices. Avoid speculation and ensure accuracy in all descriptions.
Conclusion
By adhering to these guidelines, we can ensure that our AI Agents are developed in a manner that is efficient, maintainable, and aligned with industry best practices. This will contribute to the overall success and reliability of the application.
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.
- 1mo ago First seen · 28 lines · 407 tokens per session scan A 53634a7e028a
firebase-cloud-messenger AGENTS.md is an instructions file published in the GitHub repository az-coder-123/firebase-cloud-messenger (11 stars, last pushed 6mo ago), licensed MIT. It adds 407 tokens to every session, about $0.0016 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.