Borrowing it
Nothing to install: this file belongs to richer-richard/fenestra. 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/richer-richard/fenestra/main/AGENTS.mdgit clone --depth 1 https://github.com/richer-richard/fenestraWrote 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/richer-richard/fenestra/agents-md)<a href="https://agentmods.dev/instructions/richer-richard/fenestra/agents-md"><img src="https://agentmods.dev/badge/instructions/richer-richard/fenestra/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.
<a href="https://agentmods.dev/instructions/richer-richard/fenestra/agents-md"><img src="https://agentmods.dev/badge/instructions/richer-richard/fenestra/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.03064 | $0.03064 |
| Opus 5 | $0.01532 | $0.01532 |
| Sonnet 5 | $0.00613 | $0.00613 |
| Haiku 4.5 | $0.00306 | $0.00306 |
Grade A, and why
fenestra 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 9d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building fenestra UIs as an agent
fenestra is designed so that an agent authoring a UI can see and verify its work without a display server. This file is the working manual.
The loop
- Write a view (or a full
App). - Drive it with the harness — semantic queries, not coordinates — and assert structure and messages.
- Render it headlessly to a PNG. Open and look at the PNG. Layout bugs, clipped text, and bad spacing are visible; do not skip this.
- Iterate until it looks right, then lock it with a golden test.
use fenestra::prelude::*;
use fenestra::shell::render_element;
let view: Element<()> = col().p(SP6).gap(SP4).children([
text("Hello").size(TextSize::Xl2).weight(Weight::Semibold),
button("Save").into(),
]);
let image = render_element(view, &Theme::light(), (480, 240));
image.save("preview.png").unwrap(); // now actually look at it
Headless rendering is deterministic: embedded Inter fonts, scale 1.0, reduced motion, in-memory clipboard. The same tree renders the same pixels on every machine of the same GPU class (cross-rasterizer runs use a small tolerance; see Golden tests).
Driving a real app: the harness
Harness runs the full Elm loop — dispatch, state, focus, editing —
driven by semantic queries (find things the way a user would; never
hardcode coordinates):
use fenestra::prelude::*;
use fenestra::shell::Harness;
let mut h = Harness::new(MyApp::default(), Theme::light(), (800, 600));
h.click(&by::role(Semantics::Button).name("Add")); // strict: 0 or 2+ matches panic
h.type_text("hello"); // into the focused input
h.key(KeyInput::plain(Key::Enter));
assert_eq!(h.app().items.len(), 1); // state
assert!(h.query(&by::label("hello")).is_some()); // structure (None = absent)
let msgs = h.take_messages(); // behavior: what the UI emitted
h.render().save("after.png").unwrap(); // pixels — now look at it
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.
- 9d ago First seen · 251 lines · 3,064 tokens per session scan A ef32033ffde0
fenestra AGENTS.md is an instructions file published in the GitHub repository richer-richard/fenestra (12 stars, last pushed 26d ago), licensed Apache-2.0. It adds 3,064 tokens to every session, about $0.0153 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
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.