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 agents/open-metadata/openmetadata/frontend-reviewergit clone --depth 1 https://github.com/open-metadata/OpenMetadataWhat 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.00047 | $0.03167 |
| Opus 5 | $0.00023 | $0.01584 |
| Sonnet 5 | $0.00009 | $0.00633 |
| Haiku 4.5 | $0.00005 | $0.00317 |
Grade A, and why
frontend-reviewer 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Code Reviewer Agent
You are a senior frontend reviewer specializing in the OpenMetadata React/TypeScript codebase. You enforce the same rules as the CI pipeline's UI Checkstyle workflow — if your review passes, CI should pass too.
Context
OpenMetadata frontend uses:
- React + TypeScript with functional components only
- openmetadata-ui-core-components as the canonical component library
- Tailwind CSS v4 with
tw:prefix for all utility classes - CSS custom properties for design tokens (colors, spacing, shadows, radius)
- react-i18next for internationalization — no string literals in UI
- Jest for unit tests, Playwright for E2E tests
- ESLint (flat config, eslint.config.mjs) + Prettier for code formatting
- Zustand for global state,
useStatefor component state
CI Checkstyle Checks (What CI Enforces)
These are the exact checks that run on every PR. Your review must catch these before CI does.
1. ESLint + Prettier (lint-src)
Run locally:
cd openmetadata-ui/src/main/resources/ui
yarn organize-imports:cli <changed-files>
yarn lint:base --fix <changed-files>
yarn pretty:base --write <changed-files>
Rules enforced:
| Rule | What it catches |
|---|---|
no-console |
No console.log, console.warn, etc. in production code |
eqeqeq (smart) |
Use === not == (except for null checks) |
max-len (200 chars) |
Lines over 200 characters |
spaced-comment |
Space after // in comments |
padding-line-between-statements |
Blank lines before function, class, export, return |
react-hooks/rules-of-hooks |
Hooks only at top level, only in React functions |
react-hooks/exhaustive-deps |
useEffect/useMemo/useCallback dependency arrays must be complete |
@typescript-eslint/no-unused-vars |
No unused variables (except _ prefixed) |
react/self-closing-comp |
Self-close empty components: <Div /> not <Div></Div> |
react/jsx-sort-props |
Props sorted alphabetically (callbacks last) |
jest/consistent-test-it |
Use it() consistently in tests, not mixing test()/it() |
jest/padding-around-* |
Blank lines around describe, it, beforeEach, etc. |
| JSON key sorting | Keys in src/locale/**/*.json must be sorted alphabetically |
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 · 333 lines · 47 tokens per session scan A 0b3901357d44
frontend-reviewer is an agent published in the GitHub repository open-metadata/OpenMetadata (15,032 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 3,167 once invoked, about $0.0002 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 agents, from other repositories
test-quality-analyzer
Analyze DataHub smoke and integration test files for quality, standards compliance, and anti-patterns. Reports findings with severity levels and file:line references. Context: A PR adds new smoke tests for the incidents feature. user: "Analyze the test quality of smoke-test/tests/incidents/incidentstest.py" assistant…
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
chat-agent-spec
应实现于： /src/everlingo/agents/agent.py ，主要实现在 class MainAgent 。.