Borrowing it
Nothing to install: this file belongs to snowdreamtech/frp. 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/snowdreamtech/frp/main/.github/instructions/rules.instructions.mdgit clone --depth 1 https://github.com/snowdreamtech/frpWrote 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/snowdreamtech/frp/rules)<a href="https://agentmods.dev/instructions/snowdreamtech/frp/rules"><img src="https://agentmods.dev/badge/instructions/snowdreamtech/frp/rules.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.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
frp rules.instructions.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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- template rules.instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨 CRITICAL SYSTEM INSTRUCTION 🚨
Before answering ANY prompt or executing ANY code in this repository, you MUST first read and strictly adhere to ALL the rules defined in the following directory:
Step 1: Read ALL Core Rule Files
📁 .agent/rules/ — Read in numerical order:
.agent/rules/01-general.md— Language, communication, idempotency, cross-platform, network, security & audit.agent/rules/02-coding-style.md— Commit messages, code quality, error handling, documentation, naming conventions.agent/rules/03-architecture.md— Project structure, AI IDE integration, design principles.agent/rules/04-security.md— Credentials, access control, encryption, scanning, incident response.agent/rules/05-dependencies.md— Locking, integrity, auditing, release process, changelog.agent/rules/06-ci-testing.md— Test types, CI pipeline, test data, fast feedback, quality gates.agent/rules/07-git.md— Commits, branching, pull requests, code review, history hygiene.agent/rules/08-dev-env.md— Environment consistency, dev container, scripts, pre-commit hooks, debugging.agent/rules/09-ai-interaction.md— Safety boundaries, code generation, communication, context handling, quality.agent/rules/10-ui-ux.md— Styling, componentization, accessibility, performance, i18n (frontend projects only).agent/rules/11-deployment.md— Containerization, secrets, deployment pipeline, IaC, observability & DR
Step 2: Read Relevant Language & Framework Rule Files
After reading the core rules, inspect the project's file structure and configuration files to identify the languages and frameworks in use. Then read the corresponding rule files from .agent/rules/.
Why This File Exists
This project uses a unified rule system to ensure consistent AI behavior
across all AI-powered IDEs and tools (Cursor, Windsurf, GitHub Copilot,
Cline, Claude, Gemini, Trae, Roo Code, Augment, Amazon Q, Kiro,
Continue, Junie, etc.). This file is a redirect entry point —
the actual rules live in .agent/rules/ as the Single Source of Truth.
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.
- yesterday First seen · 40 lines · 543 tokens per session scan A 45f7f745953f
frp rules.instructions.md is an instructions file published in the GitHub repository snowdreamtech/frp (908 stars, last pushed 5d ago), licensed MIT. It adds 543 tokens to every session, about $0.0027 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-05.
Other instructions, from other repositories
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.
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).
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).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.