Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/crackenreleased/boarderless.app_mcp/agents-mdgit clone --depth 1 https://github.com/CrackenReleased/boarderless.app_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/crackenreleased/boarderless.app_mcp/agents-md)<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="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.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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 5d 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 — 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.
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.
- 5d ago First seen · 55 lines · 689 tokens per session scan A b0626a101976
boarderless.app_MCP AGENTS.md is an instructions file published in the GitHub repository CrackenReleased/boarderless.app_MCP (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 689 tokens to every session, about $0.0034 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
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).
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.
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.
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.
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).