Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/instructions/yavorsky/unbuilt.app/agents-md)<a href="https://agentmods.dev/instructions/yavorsky/unbuilt.app/agents-md"><img src="https://agentmods.dev/badge/instructions/yavorsky/unbuilt.app/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.01091 | $0.01091 |
| Opus 5 | $0.00545 | $0.00545 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
unbuilt.app 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — unbuilt.app
Tech stack detection for websites via Playwright + pattern matching.
Project Structure
Monorepo (yarn workspaces + turborepo):
apps/cli/ — CLI tool (`unbuilt <url>`)
apps/web/ — Next.js web app (unbuilt.app)
packages/analyzer/ — Orchestrates detection: navigates page, runs all detectors, two-pass analysis
packages/features/ — Detection categories & patterns (this is where you add new detections)
packages/helpers/ — Shared utilities
packages/resources/— Resource tracking (scripts, stylesheets, etc.)
How Detection Works
- Resources are collected from a live page (scripts, stylesheets, documents, headers, filenames)
- Patterns match against those resources using regex and browser checks
- Two-pass analysis: first pass detects everything independently, second pass runs
dependencieschecks so categories can reference each other's results - Each category returns:
{ name, confidence, detectedFeatures, secondaryMatches }
Pattern Interface
interface Pattern {
score: number; // Weight (0-1). Higher = stronger signal
name: string; // Identifier for this pattern
scripts?: RegExp[]; // Match against JS bundle contents
stylesheets?: RegExp[]; // Match against CSS contents
documents?: RegExp[]; // Match against HTML document
headers?: Record<string, RegExp>; // Match against HTTP headers
filenames?: RegExp[]; // Match against resource URLs
browser?: (page, browser) => boolean | Promise<boolean>; // Runtime check
dependencies?: (analysis) => boolean; // Cross-category dependency check (2nd pass)
}
Key Types
Pattern—packages/features/src/types/pattern.tsFeatureResult—packages/features/src/types/feature.tsCalculationResult—packages/features/src/types/feature.tsAnalysisFeatures—packages/features/src/types/analysis.tsAnalyzeResult—packages/analyzer/src/types.ts
Adding a Pattern to an Existing Category
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 · 130 lines · 1,091 tokens per session scan A 777cc52bd12e
unbuilt.app AGENTS.md is an instructions file published in the GitHub repository yavorsky/unbuilt.app (92 stars, last pushed 16d ago), licensed MIT. It adds 1,091 tokens to every session, about $0.0055 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-30.
Other instructions, from other repositories
Browser4 CLAUDE.md
Claude Code instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
cc-websearch CLAUDE.md
Claude Code instructions for Djarvur/cc-websearch, covering project, constraints, technology stack, what not to add and conventions.
fix-quera AGENTS.md
Instructions for AlirezaKeshavarz83/fix-quera, covering agent guidance, project shape, visual style, quera page data findings and compatibility findings.
sniff AGENTS.md
AGENTS.md instructions for Aboudjem/sniff, covering agents.md: sniff, what this repo is, how an agent should use sniff, handling the playwright setup gate and finding output schema.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
sendblue-browser-use AGENTS.md
Instructions for sendblue-api/sendblue-browser-use, covering agents.md — sendblue-browser-use, what this repo is, setup, common commands and health (no auth).