Borrowing it
Nothing to install: this file belongs to valternunez/refract. 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/valternunez/refract/main/AGENTS.mdgit clone --depth 1 https://github.com/valternunez/refractWrote 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/valternunez/refract/agents-md)<a href="https://agentmods.dev/instructions/valternunez/refract/agents-md"><img src="https://agentmods.dev/badge/instructions/valternunez/refract/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/valternunez/refract/agents-md"><img src="https://agentmods.dev/badge/instructions/valternunez/refract/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.00988 | $0.00988 |
| Opus 5.5 | $0.00395 | $0.00395 |
| Sonnet 5.5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
refract 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refract — agent playbooks
Short recipes for when to reach for Refract and what to do with the output. Each is 5–15 lines: when to use it, the calls in order, what to look for.
render_responsiveis live and returns, in one response: structured findings (JSON keyed by preset), absolute saved paths, and a downscaled preview per viewport.
Playbook: verify a responsive bug fix
When: you changed CSS to fix a layout bug at a specific width.
render_responsive({ url: "http://localhost:3000/page", viewports: ["iphone-15", "ipad-mini", "macbook-air-13"] })- Look at the returned preview for the viewport you fixed.
- Confirm the
horizontal_overflow/element_clippedfinding for that viewport is gone from the response. If it's still present, the fix didn't take.
Playbook: visual-diff before merge
When: you want before/after proof a change didn't break the layout anywhere.
- On the base branch — MCP:
diff_responsive({ url, update: true }), or CLI:refract diff <url> --update --freeze— snapshots the baseline into./refract-baseline/{preset}.png. - Apply the change, then compare — MCP:
diff_responsive({ url })(returns a status per viewport + a diff image for each change), or CLI:refract diff <url> --freeze. unchangedeverywhere → safe to merge. Anychangedgives the % of pixels and a diff image/report.html(baseline │ current │ diff). The CLI exits non-zero on any change, so it drops straight into CI. Re-run withupdate/--updateto accept. Tip: passinjectCssto hide live clocks/ads so they don't read as false changes.
Playbook: screenshot a page behind a login
When: the page you need to verify is auth-gated (a dashboard, account settings).
- Get a Playwright storage-state JSON. If the project has e2e auth states (e.g.
e2e/.auth/*.json), use one of those. Otherwise a human runs once:npx playwright codegen --save-storage=auth.json <login-url>, logs in, closes it. render_responsive({ url: "https://app/dashboard", storageState: "./auth.json" })- The previews show the logged-in page (not the login wall); read findings as usual. If you still see the login screen, the state is stale — regenerate 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.
- 2mo ago First seen · 66 lines · 988 tokens per session scan A a1a7d7eb4805
refract AGENTS.md is an instructions file published in the GitHub repository valternunez/refract (0 stars, last pushed 4mo ago), licensed MIT. It adds 988 tokens to every session, about $0.0040 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.
Other instructions, from other repositories
qmax-mcp copilot-instructions.md
Copilot instructions for Quality-Max/qmax-mcp, covering qualitymax qa workflow and adjacent tools.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).