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/mattv8/ragtime/frontendgit clone --depth 1 https://github.com/mattv8/ragtimeWhat 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.02127 | $0.02127 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00425 | $0.00425 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
ragtime frontend.instructions.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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ragtime Frontend - Design System
Ragtime's UI is token-driven. Every color, radius, shadow, spacing value, and font is a CSS custom property defined in src/styles/theme.css (the base contract) and optionally overridden per theme pack under src/styles/themes/.
Component CSS must never hard-code themeable values. It should read tokens so a theme applies app-wide without per-component rules.
There are two orthogonal axes, both set as attributes on <html>:
| Axis | Attribute | Values | Storage key | Default |
|---|---|---|---|---|
| Theme pack | data-theme-pack |
default (attribute absent), serif |
ragtime-theme-pack |
default |
| Color mode | data-theme |
light, dark, system (attribute absent) |
ragtime-theme |
system |
They compose: for example, data-theme-pack="serif" + data-theme="light" produces the serif pack's parchment light palette. Both are applied before first paint by the inline guard in index.html to avoid a flash of the wrong theme, and at runtime via src/theme (setThemePack, setColorMode).
Persistence & Precedence
- Theme pack resolution is
user saved choice -> global default -> default;resolveThemePackId(...)is the source of truth. - The theme registry (
THEME_PACKS) is canonical for available packs, user-menu cycling order, and Settings cards. There are currently onlydefaultandserif. localStorageis advisory only:getStoredThemePack()andgetStoredColorMode()are guarded and fall back to defaults if storage is unavailable or invalid.setThemePack()andsetColorMode()remove the corresponding HTML attribute and clear the storage key when switching back todefaultorsystem.- User-menu theme changes are applied immediately in the UI and then saved best-effort to the account; the optimistic local theme stays in place even if the network save fails.
- The global default theme is changed in Settings and is intended for admins; a per-user choice always overrides it.
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 · 111 lines · 2,127 tokens per session scan A 96110f04fc11
ragtime frontend.instructions.md is an instructions file published in the GitHub repository mattv8/ragtime (33 stars, last pushed 5d ago), licensed MIT. It adds 2,127 tokens to every session, about $0.0106 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.