What is boarderless.app_MCP AGENTS.md?

Repository instructions for Boarderless, a visual canvas application, and its MCP servers, connectors, tests, scripts, and agents. They require visible browser operation and define a detailed standard for finished work.

Guiding agents working on Boarderless-related code, especially browser automation, MCP features, tests, scripts, and completion checks.

They set safety and quality rules, including keeping browser actions observable and verifying that the rules remain enforced.

How CrackenReleased/boarderless.app_MCP configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to CrackenReleased/boarderless.app_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.

Copy the file

curl -O https://raw.githubusercontent.com/CrackenReleased/boarderless.app_MCP/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/CrackenReleased/boarderless.app_MCP

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/crackenreleased/boarderless.app_mcp/agents-md/github.svg)](https://agentmods.dev/instructions/crackenreleased/boarderless.app_mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/crackenreleased/boarderless.app_mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/crackenreleased/boarderless.app_mcp/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/crackenreleased/boarderless.app_mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/crackenreleased/boarderless.app_mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 689 This file is loaded in full into every session.

When invoked 689 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.

Model	Per session	Once invoked
Fable 5.1	$0.00689	$0.00689
Opus 5.5	$0.00276	$0.00276
Sonnet 5.5	$0.00138	$0.00138
Haiku 4.5	$0.00069	$0.00069

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

Security

Grade A, and why

boarderless.app_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 2mo 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 · 55 lines

How it starts

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

AGENTS.md — Operating Rules for Every Agent in This Repo

Read SOUL.md first. It is not decoration. It is the standard you are held to.

Permanent visible-operation law

Boarderless and every Boarderless MCP server, connector, test, script, and agent must never run, attach to, enable, recommend, or tolerate a headless or otherwise invisible browser under any circumstance. Every Ai action must occur in a real visible window with the Boarderless canvas tab brought to the front so Joel can watch, QA, learn from, and mature the product. Runtime MCP guards must reject externally supplied headless browsers, and npm run verify:visible-operation must remain part of the test suite.

The Prime Directive: ZERO APATHY

Never do the minimum. The thing in your lap gets finished, polished, and made beautiful — every time, without being asked twice.

"Done" in this repo means done like the castle wall: 12 feet wide, 30 feet tall, stone — two laden chariots can race across the top and not a pebble moves. Unmatched. Imposing. Cannot be challenged. For what it is, perfect.

What ZERO APATHY means in practice

If it's HTML, it's alive. Buttons click. Links go somewhere real (play.boarderless.app unless told otherwise). Hover states respond. Never ship a styled <div> pretending to be a button.
Finish the whole thought. If making it fully functional costs ten more minutes than making it look functional, spend the ten minutes. A mockup is only acceptable when the user explicitly asked for a mockup.
Look at your own work before delivering it. Render it, run it, read it back. Overlapping text, broken layout, dead code — if the user can see it, you should have seen it first.
Fix the class of problem, not the instance. One dead button means you check every button in every file you touched.
Match the brand, every time. Colors, type, spacing, and voice come from the existing system (see ads/AD_SPEC.md, docs/features_catalog.md). Never freelance a new look because it was faster.

Read the full file on GitHub · 55 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.

2mo ago First seen · 55 lines · 689 tokens per session scan A b0626a101976

Subscribe to this mod's changes

boarderless.app_MCP AGENTS.md is an instructions file published in the GitHub repository CrackenReleased/boarderless.app_MCP (1 stars, last pushed today), licensed Apache-2.0. It adds 689 tokens to every session, about $0.0028 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.

boarderless.app_MCP AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
boarderless.app_MCP AGENTS.mdCrackenReleased/boarderless.app_MCP	Instructions file	1	today	Apache-2.0	A	689	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

boarderless.app_MCP: Instructions file for Codex