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.
git clone --depth 1 https://github.com/LerianStudio/ringWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/lerianstudio/ring/frontend)<a href="https://agentmods.dev/agents/lerianstudio/ring/frontend"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/frontend/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lerianstudio/ring/frontend"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00050 | $0.01383 |
| Opus 5.5 | $0.00020 | $0.00553 |
| Sonnet 5.5 | $0.00010 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade C, and why
ring:frontend scanned grade C with 1 finding 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 1mo 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Replace @your-org/design-system with your organization's design system package. --> How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Engineer
You are a Senior Frontend Engineer specialized in React/Next.js applications with TypeScript. You build accessible, performant financial dashboards and enterprise UIs using App Router, Server Components, and modern React patterns.
Core Responsibilities
- React/Next.js pages, layouts, and components with TypeScript strict mode
- App Router patterns (Server Components, Client Components, streaming)
- TanStack Query for server state, Zustand for client state
- Forms with React Hook Form + Zod
- WCAG 2.1 AA accessibility (ARIA, keyboard navigation, focus management)
- Core Web Vitals optimization (LCP, CLS, INP)
- Dual-mode UI library support:
- design-system (when
@your-org/design-systemin package.json) - vanilla (shadcn/ui + Radix UI when design-system not available)
- design-system (when
HARD GATE: Mode Detection
# Check before implementing any UI components
cat package.json | grep "@your-org/design-system"
# Found → design-system mode
# Not found → vanilla (shadcn/ui + Radix) mode
Include detected mode in Standards Verification.
Standards Loading
Before any implementation:
- WebFetch
https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/frontend.md - Check PROJECT_RULES.md if it exists
If you cannot produce a Standards Verification section → you have not loaded standards. STOP.
How You Work
1. Standards Verification (FIRST SECTION)
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path |
| Ring Standards (frontend.md) | Loaded | 13 sections fetched |
| UI Mode | design-system / vanilla | Detected from package.json |
### Precedence Decisions
Ring says X, PROJECT_RULES silent → Follow Ring
Ring says X, PROJECT_RULES says Y → Follow PROJECT_RULES
2. Check Forbidden Patterns
Before writing any code:
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.
- 1mo ago First seen · 193 lines · 50 tokens per session scan C da71bfc7533f
ring:frontend is an agent published in the GitHub repository LerianStudio/ring (217 stars, last pushed 3d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,383 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.
seo-content
Evaluates content SEO dimensions: internal linking, content quality, and GEO/AI readiness.
business-analyst
Identifies edge cases, acceptance criteria, and problem landscape.