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.
npx agentmods add instructions/rustfs/launcher/gemini-mdgit clone --depth 1 https://github.com/rustfs/launcherWhat 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 | $0.00903 | $0.00903 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
launcher GEMINI.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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Context: RustFS Launcher
Project Overview
RustFS Launcher is a desktop GUI application designed to configure, launch, and monitor the rustfs binary. It bridges a robust Rust backend with a reactive web-based frontend using the Tauri framework.
- Frontend: Built with Leptos (Rust web framework), providing a type-safe, reactive UI for user input and real-time log streaming.
- Backend: A Tauri (Rust) application that manages the lifecycle of the external
rustfsprocess, captures its stdout/stderr, and streams these logs to the frontend via events.
Architecture & Key Components
Backend (src-tauri/)
The backend acts as the process manager and native layer.
src-tauri/src/lib.rs: Application entry point. Sets up the Tauri builder, lifecycle hooks, and registers commands.src-tauri/src/commands.rs: Defines the API exposed to the frontend (e.g.,launch_rustfs,get_app_logs).src-tauri/src/process.rs: Core logic for locating therustfsbinary (checks multiple paths), diagnosing it, and spawning the child process. Captures output streams.src-tauri/src/state.rs: Manages global, thread-safe application state (process handles, log history) and emits real-time events (app-log,rustfs-log) to the frontend.
Frontend (src/)
The frontend is a Single Page Application (SPA) compiled to WebAssembly.
src/main.rs: Leptos entry point, mounts the application.src/app.rs: The main UI component. It handles:- Configuration: Inputs for Host, Port, and Mountpoint.
- Commands: Invokes
launch_rustfsvia Tauri'sinvokesystem. - Events: Listens for
APP_LOG_EVENTandRUSTFS_LOG_EVENTto update the log console in real-time.
src/logs.css: Styles specific to the log viewer component.
Building and Running
Prerequisites
- Rust: Standard toolchain (
cargo,rustup). - Node.js: Required for Tauri's CLI and frontend asset bundling.
- Trunk: The WASM web application bundler (
cargo install trunk).
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.
- yesterday First seen · 71 lines · 903 tokens per session scan A 9e1d3eb52d5e
launcher GEMINI.md is an instructions file published in the GitHub repository rustfs/launcher (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 903 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.
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.
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).
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.
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).
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.
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.