console AGENTS.md

Project instructions for the RustFS Console web application, covering its folders, development commands, tests, and coding rules. They explain where application code, UI components, translations, assets, and tests belong.

In plain words
What is it for?
Use them when developing or reviewing the RustFS Console, especially for UI, shared utilities, configuration, translations, and tests.
Why use it?
They help coding agents make changes in the correct part of the application and meet the repository’s checks before committing.

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/console/agents-md
Clone the repo
git clone --depth 1 https://github.com/rustfs/console

Made for: Codex, OpenCode.

Per session 2,320 This file is loaded in full into every session.
When invoked 2,320 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.02320 $0.02320
Opus 5 $0.01160 $0.01160
Sonnet 5 $0.00464 $0.00464
Haiku 4.5 $0.00232 $0.00232

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

Security

Grade A, and why

console 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 · 115 lines

How it starts

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

Repository Guidelines

Rules for agents working in this repository. When a rule conflicts with what you find in the code, surface the conflict instead of silently deviating.

Project Structure & Module Organization

  • Core application lives under app/, with App Router layouts in app/(auth)/, app/(dashboard)/.
  • Supporting UI atoms live in components/; shared hooks in hooks/, shared contexts in contexts/.
  • Configuration lives in next.config.ts, app.config.ts (if present), and config/.
  • Shared utilities and lib code are in lib/; type definitions in types/.
  • i18n locale files live under i18n/locales/; their structure must match the old project — do not alter i18n layout or keys arbitrarily.
  • Static assets belong in public/ or assets/; tests in tests/ (mirror source structure).
  • UI vs feedback: components/ui/ holds presentational, declarative UI primitives (Button, Dialog). lib/feedback/ holds global imperative APIs for toast and confirm dialogs. Use @/lib/feedback/message and @/lib/feedback/dialog for imperative feedback; use @/components/ui/* for declarative UI.

Build, Test, and Development Commands

Run nvm use v22 before any pnpm command in this repository.

  • pnpm dev – start the dev server (applies theme overrides first).
  • pnpm build – production build (also type-checks); pnpm start – run it locally.
  • pnpm lint / pnpm lint:fix – run / auto-fix ESLint.
  • pnpm type-check – strict TypeScript check (applies theme overrides, then tsc --noEmit).
  • pnpm format / pnpm format:check – Prettier write / check.
  • pnpm test:run – run the test suite.

Quality Gates — must pass before every commit

  1. pnpm install --frozen-lockfile – lockfile in sync. After changing package.json, run pnpm install and commit the updated pnpm-lock.yaml; CI fails otherwise.
  2. pnpm type-check – zero type errors.
  3. pnpm lint – zero ESLint errors.
  4. pnpm format:check – consistent formatting (fix with pnpm format or pnpm lint:fix).
  5. pnpm test:run – all tests pass, and tests are updated to match the change (see Testing Guidelines).

Read the full file on GitHub · 115 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 · 115 lines · 2,320 tokens per session scan A 46c21f45b5f2

Subscribe to this mod's changes

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