Borrowing it
Nothing to install: this file belongs to sinmb79/22B-Interior-Planning-Master-MCP. 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/sinmb79/22B-Interior-Planning-Master-MCP/main/AGENTS.mdgit clone --depth 1 https://github.com/sinmb79/22B-Interior-Planning-Master-MCPWrote 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/sinmb79/22b-interior-planning-master-mcp/agents-md)<a href="https://agentmods.dev/instructions/sinmb79/22b-interior-planning-master-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sinmb79/22b-interior-planning-master-mcp/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.01422 | $0.01422 |
| Opus 5 | $0.00711 | $0.00711 |
| Sonnet 5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
22B-Interior-Planning-Master-MCP 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 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.
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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Documentation Style Guide
When writing or updating README.md or any documentation files, follow these rules strictly. These rules apply to ALL documentation tasks: new READMEs, updates, rewrites, and doc fixes.
Critical Rule: Structure Over Prose
The single most important rule: use tables and code blocks, not essays.
If you catch yourself writing more than 3 consecutive sentences without a table, code block, or heading, STOP and restructure.
BAD (essay style):
## Why This Exists
Most video tools ask for settings before they ask for taste.
That sounds efficient, but it usually produces generic work.
People do not think in "pacing_profile" and "camera_language" first.
They think in references, moods, instincts, and the strange combination
of things they already love. This project exists to close that gap.
GOOD (structured style):
## 소개 | Introduction
Shorts Engine은 좋아하는 영화, 영상 스타일, 작가 취향에서 출발해
숏폼 영상 시나리오를 자동으로 만드는 CLI 도구입니다.
Shorts Engine is a CLI tool that starts from your personal taste
and generates short-form video scenarios automatically.
Bilingual (Korean + English)
- Write every section in both Korean and English
- Korean comes first, English follows immediately after
- Section headers:
## 한글 제목 | English Title - Table content: Korean and English in the same row where practical (e.g.,
설명 Descriptioncolumn) - Blockquotes and important notices: Korean line, then English line
BAD:
## What You Need
- n8n (`localhost:5678`)
GOOD:
## 필요한 환경 | Requirements
| 구성요소 Component | 설명 Description |
|------------------|-----------------|
| **n8n** | 워크플로우 엔진 (`localhost:5678`) |
Real Examples Required
- Every feature or tool MUST include a concrete usage example
- Show actual input (what the user types/says to the AI) in a code block
- Show actual output (JSON response, generated text, file content) in a code block
- Use realistic Korean data, not placeholder text
- Examples should demonstrate end-to-end workflow, not just API signatures
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 · 195 lines · 1,422 tokens per session scan A b54c7c095b54
22B-Interior-Planning-Master-MCP AGENTS.md is an instructions file published in the GitHub repository sinmb79/22B-Interior-Planning-Master-MCP (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,422 tokens to every session, about $0.0071 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.