Borrowing it
Nothing to install: this file belongs to Skyvern-AI/rustwright. 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/Skyvern-AI/rustwright/main/AGENTS.mdgit clone --depth 1 https://github.com/Skyvern-AI/rustwrightWrote 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/skyvern-ai/rustwright/agents-md)<a href="https://agentmods.dev/instructions/skyvern-ai/rustwright/agents-md"><img src="https://agentmods.dev/badge/instructions/skyvern-ai/rustwright/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/skyvern-ai/rustwright/agents-md"><img src="https://agentmods.dev/badge/instructions/skyvern-ai/rustwright/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.00996 | $0.00996 |
| Opus 5.5 | $0.00398 | $0.00398 |
| Sonnet 5.5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
rustwright 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Instructions
Public boundary
Treat every tracked file, commit, branch name, and review artifact as if it will be publicly visible. This repository is the source of truth; a separate, reviewed sync republishes approved content to a public mirror, so every change merged here is the last gate before it can become public.
- Never add credentials, auth headers, customer data, private URLs, personal filesystem paths, employee email addresses, internal ticket identifiers, or private host/network topology.
- Do not name private repositories, packages, modules, services, or operational
incidents. Use neutral placeholders such as
<organization>,<repository>,<remote-host>, and<source-checkout>in public examples. - Keep integration tools that import or inspect private code in the private repository. Public tools must require explicit user-supplied paths and must not default to sibling checkouts.
- Keep raw benchmark data, terminal output, HAR files, environment files, and generated reports untracked. Publish only reviewed, reproducible summaries; never let a headline number rest on demo-grade or otherwise irreproducible data.
- Use a GitHub
noreplyaddress for commit author and committer identities. Automation co-author trailers must likewise use a providernoreplyaddress (for example[email protected]), never a personal or corporate mailbox. Never rewrite or force-push shared history without explicit owner approval, and never usegit push --all.
Before committing, inspect the staged diff for disclosure risks.
Pull-request review
Development checkouts push only to this repository — there is no direct push to
the public mirror; the reviewed sync is the only path content takes to become
public. Every pull request opened here is reviewed automatically by
.github/workflows/claude-code-review.yml, which loads its prompt from
.github/prompts/code-review.md on the pull request's base branch (so an
untrusted pull request cannot alter its own review) and posts a single comment.
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.
- 1mo ago First seen · 89 lines · 996 tokens per session scan A f5833d4d77a0
rustwright AGENTS.md is an instructions file published in the GitHub repository Skyvern-AI/rustwright (935 stars, last pushed 11d ago), licensed MIT. It adds 996 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-30.
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.