What is glory AGENTS.md?

A contributor guide for Glory, an experimental Rust web framework. It explains its component system, reactive values, browser and server rendering, packages, and planned features.

It is for navigating the Rust crates, working with browser or server-rendered interfaces, using the framework’s reactive types, handling routing, and understanding the command-line build tool.

It gives coding agents the framework’s structure and rules, reducing confusion when changing components, reactive behavior, rendering, routing, or build tooling.

glory AGENTS.md — Instructions file by glory-rs

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/glory-rs/glory/agents-md

Clone the repo

git clone --depth 1 https://github.com/glory-rs/glory

Made for: Codex, OpenCode.

Per session 2,075 This file is loaded in full into every session.

When invoked 2,075 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.

Model	Per session	Once invoked
Fable 5	$0.02075	$0.02075
Opus 5	$0.01038	$0.01038
Sonnet 5	$0.00415	$0.00415
Haiku 4.5	$0.00208	$0.00208

Measured 2d ago against content hash f0ce123a161a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

glory 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 2d 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.

AGENTS.md · 152 lines

How it starts

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

AGENTS.md

Project conventions and design guardrails for AI coding agents and contributors. Companion to README.md. For the broader analysis and the prioritised backlog see _report.md and _todos.md.

What Glory is

Glory is an experimental Rust web framework. Components are built as builder-pattern Rust types (div().class("...").on(click, ...)), not via an rsx! / JSX macro. The reactive primitive is Cage<T> (mutable) / Bond<T> (derived) / Lotus<T> (the read-only union). Targets today: browser (CSR via wasm-bindgen) and SSR (HTML string output, integrated with Salvo). Roadmap: desktop webview, native rendering, LiveView-style server driving — see _report.md §3 / _todos.md §3–§4.

Crate layout

crates/
  core/         signals, view/widget/scope/node, web/csr + web/ssr,
                widgets (Each / Switch / Loader), SSR holder
  glory/        thin re-export front door, depends on core (+ optional routing)
  routing/      client-side router (currently wasm32-only)
  cli/          glory-cli build tool (wasm compile, css, hot reload server)
  hot-reload/   placeholder / partial; AST-diff types for future hot reload
examples/       per-app crates (counter, todomvc, hackernews-salvo, ssr-*, ...)

Feature flags and combinations

glory-core features (also re-exported through glory):

web-csr — client-side rendering in the browser. Implies single-app.
web-ssr — server-side rendering, in-memory Node tree → HTML string.
salvo — Salvo HTTP integration, implies web-ssr.
single-app — internal. Automatic with web-csr. Switches the reactive scheduler to a single global instance instead of HolderId-keyed thread locals. Don't toggle manually outside CSR.

Never enable web-csr + web-ssr in the same build. They define Node incompatibly (web_sys::Element vs an in-memory struct). Tests rely on this exclusion — see [package.metadata.cargo-all-features].skip_feature_sets.

Read the full file on GitHub · 152 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.

2d ago First seen · 152 lines · 2,075 tokens per session scan A f0ce123a161a

Subscribe to this mod's changes

glory AGENTS.md is an instructions file published in the GitHub repository glory-rs/glory (43 stars, last pushed 20d ago), licensed MIT. It adds 2,075 tokens to every session, about $0.0104 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.

Frontend Languages Rust

glory AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

AGENTS.md

What Glory is

Crate layout

Feature flags and combinations

What this file has done since we first saw it

Other instructions, from other repositories

cli AGENTS.md

turso AGENTS.md

intelligent-terminal rust.instructions.md

Browser4 CLAUDE.md

ton-rs AGENTS.md

cli AGENTS.md