launcher AGENTS.md

A project instruction guide for RustFS Launcher, a desktop application with a Rust backend and a web-based interface.

In plain words
What is it for?
Use it when developing, running, testing, or packaging the launcher with Leptos, Tauri, and RustFS binaries.
Why use it?
It explains the repository layout, build steps, supported development commands, and release process so contributors can work without guessing.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/rustfs/launcher/agents-md
Clone the repo
git clone --depth 1 https://github.com/rustfs/launcher

Made for: Codex, OpenCode.

Per session 896 This file is loaded in full into every session.
When invoked 896 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00896 $0.00896
Opus 5 $0.00448 $0.00448
Sonnet 5 $0.00179 $0.00179
Haiku 4.5 $0.00090 $0.00090

Measured yesterday against content hash 8ad56f66946a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

launcher 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 yesterday.

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.

AGENTS.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Use this guide when contributing to RustFS Launcher; it highlights the project layout, tooling, and expectations.

Project Structure & Module Organization

  • src/: Leptos client entrypoint (main.rs), UI composition (app.rs), and contextual styles (logs.css).
  • src-tauri/src/: Tauri backend modules: commands.rs for invokable actions, process.rs for RustFS binary orchestration, state.rs for shared application state, plus error types.
  • src-tauri/binaries/: Platform-specific RustFS executables fetched by the build scripts; keep this directory untracked in Git.
  • public/: Static assets bundled by Trunk (leptos.svg, tauri.svg).
  • Trunk.toml and tauri.conf.json: runtime configuration for the web client and desktop shell.

Build, Test, and Development Commands

  • ./build.sh (macOS/Linux) or build.bat (Windows): download the matching RustFS binary into src-tauri/binaries/.
  • cargo tauri dev: launch the desktop shell with hot reload across the Rust backend and Leptos UI.
  • trunk serve --port 1421: run the Leptos client in a browser-only workflow using the Trunk.toml settings.
  • cargo tauri build: produce distributable desktop bundles.
  • cargo fmt --all and cargo clippy --workspace --all-targets: enforce formatting and linting before pushing.
  • ./scripts/check-upstream-version.sh: check for new versions from upstream rustfs/rustfs repository.

Automated Build & Release

The repository includes automated workflows to keep in sync with upstream rustfs/rustfs releases:

Upstream Version Sync (.github/workflows/upstream-sync.yml)

  • Scheduled Check: Runs hourly to check https://version.rustfs.com/latest.json for new rustfs/rustfs releases.
  • Automatic Trigger: When a new upstream version is detected, it automatically creates a corresponding git tag and triggers the build workflow.
  • Manual Trigger: Can be manually triggered via GitHub Actions with an optional force_build parameter.
  • Version Tracking: Compares upstream release tags with local repository tags to detect updates.

Read the full file on GitHub · 55 lines

Changes

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.

  1. yesterday First seen · 55 lines · 896 tokens per session scan A 8ad56f66946a

Subscribe to this mod's changes

launcher AGENTS.md is an instructions file published in the GitHub repository rustfs/launcher (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 896 tokens to every session, about $0.0045 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens