agentmods.dev

flaredeck: Instructions file for Codex

AGENTS.md

flaredeck AGENTS.md is an instructions file for Codex, OpenCode from milzamsz/flaredeck. It costs 3,154 tokens per session, scanned A, original, MIT.

Repository-wide instructions for FlareDeck, a local desktop control panel for developing with Cloudflare Tunnels.

In plain words
What is it for?
They guide changes across the desktop interface, command-line tool, and local MCP server while preserving the project's fixed boundaries and rules.
Why use it?
They define which project documents and design decisions take priority when requirements or existing code disagree.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is milzamsz/flaredeck's own configuration. It tells Codex and OpenCode how to work on flaredeck itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything flaredeck configures →

not rated 5repo 28d ago A scan 3,154 tokens original MIT
View source ↗ milzamsz/flaredeck flaredeck.dev
Reuse

Borrowing it

Nothing to install: this file belongs to milzamsz/flaredeck. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/milzamsz/flaredeck/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/milzamsz/flaredeck

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for flaredeck AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/milzamsz/flaredeck/agents-md/github.svg)](https://agentmods.dev/instructions/milzamsz/flaredeck/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/milzamsz/flaredeck/agents-md"><img src="https://agentmods.dev/badge/instructions/milzamsz/flaredeck/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.

agentmods 80×15 button for flaredeck AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/milzamsz/flaredeck/agents-md"><img src="https://agentmods.dev/badge/instructions/milzamsz/flaredeck/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,154 This file is loaded in full into every session.
When invoked 3,154 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03154 $0.03154
Opus 5.5 $0.01262 $0.01262
Sonnet 5.5 $0.00631 $0.00631
Haiku 4.5 $0.00315 $0.00315

Measured 1mo ago against content hash e61606694f18, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flaredeck 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.

AGENTS.md · 389 lines

How it starts

The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file applies to the entire flaredeck repository. It is the always-on operating contract for coding agents and human contributors using AI-assisted development.

1. Mission

FlareDeck is a local-first desktop control panel for Cloudflare Tunnel development. The enhancement roadmap adds a trusted local development control plane that can be accessed through the desktop UI, a headless CLI, and a local MCP server.

FlareDeck is not an embedded AI application, a hosted orchestration service, a general-purpose shell runner, or a production deployment platform.

2. Source-of-truth hierarchy

When information conflicts, use this order:

  1. PRODUCT-SCOPE.md
  2. Approved ADRs under docs/adr/
  3. DOMAIN-MODEL.md
  4. ARCHITECTURE.md
  5. TECHNICAL.md
  6. Detailed specifications under docs/specs/
  7. PLAN.md
  8. Active task specification
  9. Existing implementation

The existing implementation is evidence of current behavior. It does not automatically override approved architecture. Report conflicts before implementing a material behavior change.

3. Hard invariants

These rules may not be changed without an explicit product decision and approved ADR:

  1. One profile equals one Cloudflare Tunnel and one API-token identity.
  2. API tokens are never stored in plaintext and never returned through UI, CLI, MCP, logs, or audit events.
  3. The existing keychain and encrypted fallback remain the only sanctioned token-write paths.
  4. Profile creation must verify required access before mutating local or Cloudflare state.
  5. Ingress configuration preserves the final catch-all http_status:404 rule.
  6. WSL loopback-origin rewriting remains supported.
  7. Process lifecycle remains platform-aware, including process-tree termination and crashloop protection.
  8. Desktop, CLI, and MCP interfaces use shared Rust application services.
  9. The MCP server uses local stdio for the MVP and does not bind a network listener.
  10. No CLI or MCP operation accepts an arbitrary shell command.
  11. A workspace runtime may start only from a validated manifest with an active local trust approval for the current fingerprint.
  12. MCP callers cannot approve workspace trust.
  13. Stop and cleanup operations are idempotent and ownership-aware.
  14. New Cloudflare endpoints require scope analysis and actionable error hints.
  15. Existing updater signing assumptions must not be changed casually.

Read the full file on GitHub · 389 lines

Changes

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.

  1. 1mo ago First seen · 389 lines · 3,154 tokens per session scan A e61606694f18

Subscribe to this mod's changes

flaredeck AGENTS.md is an instructions file published in the GitHub repository milzamsz/flaredeck (5 stars, last pushed 28d ago), licensed MIT. It adds 3,154 tokens to every session, about $0.0126 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-31.

CloudDevOps and cloud
Related

Other instructions, from other repositories

plan-forge naming.instructions.md

Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.

srnichols/plan-forge · 1,453 tokens

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens