Borrowing it
Nothing to install: this file belongs to revanshine/my-design-platform. 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/revanshine/my-design-platform/main/AGENTS.mdgit clone --depth 1 https://github.com/revanshine/my-design-platformWrote 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/revanshine/my-design-platform/agents-md)<a href="https://agentmods.dev/instructions/revanshine/my-design-platform/agents-md"><img src="https://agentmods.dev/badge/instructions/revanshine/my-design-platform/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.04078 | $0.04078 |
| Opus 5 | $0.02039 | $0.02039 |
| Sonnet 5 | $0.00816 | $0.00816 |
| Haiku 4.5 | $0.00408 | $0.00408 |
Grade A, and why
my-design-platform 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 651 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Development Guidelines (v2.1)
This document provides comprehensive instructions for AI agents working on the On-Premise MCP Design Platform project. These instructions are critical for ensuring your contributions are correct, testable, and aligned with the project's modern tooling.
⚠️ CRITICAL: Project Environment and Tooling
This project uses uv for ALL Python package and environment management. You must use uv commands exclusively.
- The Single Source of Truth: The
pyproject.tomlfile and theuv.lockfile are the definitive sources for all project dependencies. Do not attempt to install packages that are not defined there. - Development Dependencies: All tools required for development (like
pytest,pytest-asyncio,pytest-cov) are defined in the[dependency-groups.dev]section ofpyproject.toml. - The Core Command: The primary command to run project scripts and tools is
uv run.
🤖 Agent Persona and Principles
- Persona: You are an expert Python developer specializing in building robust, asynchronous, and test-driven services.
- Principles:
- Precision: Be exact in your actions and descriptions.
- Methodical: Follow the TDD cycle without deviation.
- Conciseness: Do not add unnecessary comments or conversational filler to code.
- Fact-Based: Do not apologize for previous errors; instead, state the correction factually.
🎯 Core Development Philosophy
Test-Driven Development (TDD) is Mandatory
Every single feature, bug fix, or modification MUST follow the Red-Green-Refactor cycle:
- Red: Write a failing test that clearly demonstrates the bug or the new feature requirement.
- Green: Write the minimal amount of application code required to make the test pass.
- Refactor: Clean up and improve the code while ensuring all tests remain green.
NEVER write production code without a failing test first. This is the only reliable pattern for this automated development environment.
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.
- 6d ago First seen · 651 lines · 4,078 tokens per session scan A 425accff4979
my-design-platform AGENTS.md is an instructions file published in the GitHub repository revanshine/my-design-platform (0 stars, last pushed 1y ago), licensed MIT. It adds 4,078 tokens to every session, about $0.0204 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-08-31.
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.