Borrowing it
Nothing to install: this file belongs to lie5860/openai-search-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lie5860/openai-search-mcp/main/.claude/commands/trellis/check-frontend.mdgit clone --depth 1 https://github.com/lie5860/openai-search-mcpWrote 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/commands/lie5860/openai-search-mcp/check-frontend)<a href="https://agentmods.dev/commands/lie5860/openai-search-mcp/check-frontend"><img src="https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/check-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/commands/lie5860/openai-search-mcp/check-frontend"><img src="https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/check-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.00000 | $0.00156 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
check-frontend 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 11d 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.
This is a copy
100% identical to check-frontend — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Check if the code you just wrote follows the frontend development guidelines.
Execute these steps:
- Run
git statusto see modified files - Read
.trellis/spec/frontend/index.mdto understand which guidelines apply - Based on what you changed, read the relevant guideline files:
- Component changes →
.trellis/spec/frontend/component-guidelines.md - Hook changes →
.trellis/spec/frontend/hook-guidelines.md - State changes →
.trellis/spec/frontend/state-management.md - Type changes →
.trellis/spec/frontend/type-safety.md - Any changes →
.trellis/spec/frontend/quality-guidelines.md
- Component changes →
- Review your code against the guidelines
- Report any violations and fix them if found
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.
- 11d ago First seen · 14 lines · 0 tokens per session scan A 5e8e3b682032
check-frontend is a command published in the GitHub repository lie5860/openai-search-mcp (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 156 tokens. A static security scan graded it A with 0 findings. It is 100% identical to check-frontend, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
critique
Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table, no code edits unless asked. Use when the user wants a design review, says "what's wrong with this UI", or needs a second opinion before a handoff or presentation.
check-architecture
Angular Architecture Review.
react-patterns
Review React code for performance and composition patterns — 50+ rules ranked by impact.
fec-review
Conduct a standardized review of the specified file or recently changed front-end code, output a graded review report and save it as a Markdown file.
web-review
Review a web (HTML5) project for structure, architecture, maintainability, and risk.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.