Rayfin is a managed Backend-as-a-Service platform that creates and operates application backends from data models defined with TypeScript decorators. It provides databases, authentication, APIs, storage, and hosting for teams building applications. Its catalogue skill and plugin help coding agents create and work with Rayfin projects.
Borrowing it
Nothing to install: this file belongs to microsoft/rayfin. 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/microsoft/rayfin/main/.github/instructions/md.instructions.mdgit clone --depth 1 https://github.com/microsoft/rayfinWrote 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/microsoft/rayfin/md)<a href="https://agentmods.dev/instructions/microsoft/rayfin/md"><img src="https://agentmods.dev/badge/instructions/microsoft/rayfin/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/microsoft/rayfin/md"><img src="https://agentmods.dev/badge/instructions/microsoft/rayfin/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.00861 | $0.00861 |
| Opus 5.5 | $0.00344 | $0.00344 |
| Sonnet 5.5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
rayfin md.instructions.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 8d 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.
What it actually says
IMPORTANT: Strictly follow all markdownlint rules below when generating markdown files.
Comprehensive list of all markdownlint rules:
- MD001/heading-increment: Heading levels should only increment by one level at a time
- MD003/heading-style: Heading style
- MD004/ul-style: Unordered list style
- MD005/list-indent: Inconsistent indentation for list items at the same level
- MD007/ul-indent: Unordered list indentation
- MD009/no-trailing-spaces: Trailing spaces
- MD010/no-hard-tabs: Hard tabs
- MD011/no-reversed-links: Reversed link syntax
- MD012/no-multiple-blanks: Multiple consecutive blank lines
- MD014/commands-show-output: Dollar signs used before commands without showing output
- MD018/no-missing-space-atx: No space after hash on atx style heading
- MD019/no-multiple-space-atx: Multiple spaces after hash on atx style heading
- MD020/no-missing-space-closed-atx: No space inside hashes on closed atx style heading
- MD021/no-multiple-space-closed-atx: Multiple spaces inside hashes on closed atx style heading
- MD022/blanks-around-headings: Headings should be surrounded by blank lines
- MD023/heading-start-left: Headings must start at the beginning of the line
- MD024/no-duplicate-heading: Multiple headings with the same content
- MD025/single-title/single-h1: Multiple top-level headings in the same document
- MD026/no-trailing-punctuation: Avoid trailing punctuation in heading
- MD027/no-multiple-space-blockquote: Multiple spaces after blockquote symbol
- MD028/no-blanks-blockquote: Blank line inside blockquote
- MD029/ol-prefix: Ordered list item prefix
- MD030/list-marker-space: Spaces after list markers
- MD031/blanks-around-fences: Fenced code blocks should be surrounded by blank lines
- MD032/blanks-around-lists: Lists should be surrounded by blank lines
- MD033/no-inline-html: Inline HTML
- MD034/no-bare-urls: Bare URL used
- MD035/hr-style: Horizontal rule style
- MD036/no-emphasis-as-heading: Emphasis used instead of a heading
- MD037/no-space-in-emphasis: Spaces inside emphasis markers
- MD038/no-space-in-code: Spaces inside code span elements
- MD039/no-space-in-links: Spaces inside link text
- MD040/fenced-code-language: Fenced code blocks should have a language specified (use "text" if it's not a code language)
- MD041/first-line-heading/first-line-h1: First line in a file should be a top-level heading
- MD042/no-empty-links: No empty links
- MD043/required-headings: Required heading structure
- MD044/proper-names: Proper names should have correct capitalization
- MD045/no-alt-text: Images should have alternate text (alt text)
- MD046/code-block-style: Code block style
- MD047/single-trailing-newline: Files should end with a single newline character
- MD048/code-fence-style: Code fence style
- MD049/emphasis-style: Emphasis style
- MD050/strong-style: Strong style
- MD051/link-fragments: Link fragments should be valid
- MD052/reference-links-images: Reference links and images should use a label that is defined
- MD053/link-image-reference-definitions: Link and image reference definitions should be needed
- MD054/link-image-style: Link and image style
- MD055/table-pipe-style: Table pipe style
- MD056/table-column-count: Table column count
Additionally, all sentences should be on their own line.
Documentation Standards
- All markdown used for docs, READMEs, AGENTS, and instructions must pass
rush docs:lint. - Follow project-specific structure and audience guidance from
packages/guide/assets/docs/index.md,/docs/contributor/README.md, and any relevantAGENTS.mdfiles.
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.
- 8d ago First seen · 65 lines · 861 tokens per session scan A 5d79ac6f46b8
rayfin md.instructions.md is an instructions file published in the GitHub repository microsoft/rayfin (641 stars, last pushed 3d ago), licensed MIT. It adds 861 tokens to every session, about $0.0034 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-10-09.
Other instructions, from other repositories
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).