Borrowing it
Nothing to install: this file belongs to thirawat27/Ruvyxa. 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/thirawat27/Ruvyxa/main/CLAUDE.mdgit clone --depth 1 https://github.com/thirawat27/RuvyxaWrote 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/thirawat27/ruvyxa/claude-md)<a href="https://agentmods.dev/instructions/thirawat27/ruvyxa/claude-md"><img src="https://agentmods.dev/badge/instructions/thirawat27/ruvyxa/claude-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.01228 | $0.01228 |
| Opus 5 | $0.00614 | $0.00614 |
| Sonnet 5 | $0.00246 | $0.00246 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
Ruvyxa CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Instructions
Read AGENTS.md first. It is the source of truth for working in this repository:
the repository shape, the operating rules, what each check gates, and the change guidance written
from defects that actually shipped. This file does not repeat it — it orients a session and says
what is specific to working here as an agent.
What this repository is
Ruvyxa is a web framework whose compiler and server are Rust, and whose runtime and public API are TypeScript. That split is the single most important thing to hold in mind, because most of the expensive mistakes here come from one half of a rule being changed without the other:
crates/— the CLI (ruvyxa_cli), the bundler (ruvyxa_bundler: TypeScript/JSX compilation, resolution, linking, minification, source maps, boundary checks), the dev/production server (ruvyxa_dev_server), route discovery (ruvyxa_graph), middleware (ruvyxa_middleware), diagnostics, and the terminal UI.packages/—ruvyxa(the framework package, including theruntime/*.mjsmodules the Rust CLI spawns or imports by path),create-ruvyxa,@ruvyxa/core,@ruvyxa/react, four optional integrations, eleven deploy adapters, and five prebuilt CLI binaries.examples/demois the broad feature fixture and is deployable —RUV2213and the refusal of a dynamic server-components route are both gone.examples/deploy-smokeis the smallest app every self-hosted adapter can deploy, and it is what CI builds and launches on real Node, Bun, and Deno.
There is no esbuild, no Vite, no Webpack. The bundler is ours.
Working here
- Never run
git commit,git push, orgit add. The owner commits their own work. Stop at verified and reported: say what changed, what you ran, and what came back. - Preserve changes you did not make. This working tree sometimes carries the owner's own edits from
another terminal — check
git diff HEAD, not justgit diff, because staged changes do not appear in the latter. - Run the narrowest check that can fail while iterating, and the relevant subset of the full battery
before handing off. Both lists, and what each one gates, are in
AGENTS.md. - Prefer a fixture over a promise. When two implementations must agree and cannot share code, the
answer is a file in
tests/fixtures/replayed by a test in each language — not a comment saying they are kept in sync.AGENTS.mdlists the rules that drifted before they had one.
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 · 84 lines · 1,228 tokens per session scan A 399925c483ce
Ruvyxa CLAUDE.md is an instructions file published in the GitHub repository thirawat27/Ruvyxa (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,228 tokens to every session, about $0.0061 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.