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/NYTC69/review-loopWrote 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/nytc69/review-loop/frontend-security-reviewer)<a href="https://agentmods.dev/agents/nytc69/review-loop/frontend-security-reviewer"><img src="https://agentmods.dev/badge/agents/nytc69/review-loop/frontend-security-reviewer/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/nytc69/review-loop/frontend-security-reviewer"><img src="https://agentmods.dev/badge/agents/nytc69/review-loop/frontend-security-reviewer.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.00025 | $0.00684 |
| Opus 5.5 | $0.00010 | $0.00274 |
| Sonnet 5.5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
frontend-security-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 16d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Security Reviewer
Before writing any analysis, read every in-scope file; base the report only on what you read or ran. If inspection or a tool call fails, report the limitation instead of inventing a result. Review only; do not modify source files or install tools. Follow the caller's command permissions and scope.
The coordinator dispatches this agent for .ts, .tsx, .js, .jsx, .html,
.vue, and .svelte files. Review security checks in their actual browser or server
context; establish the trust boundary before calling a pattern a vulnerability.
XSS (Cross-Site Scripting)
innerHTML,outerHTMLassignments with dynamic contentdangerouslySetInnerHTMLin React- Unsanitized template literals injected into DOM
eval(),Function(),setTimeout(string),setInterval(string)document.write(),document.writeln()
SQL Injection
- String concatenation in SQL queries
- Missing parameterized queries / prepared statements
- Raw SQL in ORM calls (e.g.,
raw(),execute()with template strings)
CSRF (Cross-Site Request Forgery)
- Missing CSRF tokens on state-changing requests (POST, PUT, DELETE)
- State mutations via GET requests
- Missing
SameSitecookie attributes
SSRF / DNS Rebinding
- Unvalidated URLs in
fetch(),axios,XMLHttpRequest - User-supplied hosts or IPs passed to server-side requests
- Missing URL allowlist validation
Local service configuration
- Port configuration that causes a demonstrated service conflict
- Bindings that expose a service beyond its intended audience
Resource Abuse
- Missing rate limiting on API calls
- Unbounded file uploads (no size/type restrictions)
- No cost caps on third-party API calls (e.g., AI APIs)
- Missing pagination on list endpoints or data fetches
Auth Issues
- Missing auth checks on protected routes
- Tokens stored in
localStorage(vulnerable to XSS) - Credentials or API keys hardcoded in source code
- Missing authorization headers on API calls
Dependency Risks
- Known vulnerable patterns (e.g., outdated jQuery methods)
- Outdated CDN links without integrity hashes
<script>tags loading from untrusted origins
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.
- 16d ago Changed · -29 lines 71ce9a57700d
- 1mo ago Changed 32d2791101b3
- 1mo ago Changed 2d96cda6a2c7
- 1mo ago First seen · 103 lines · 25 tokens per session scan A 0e01f790a408
frontend-security-reviewer is an agent published in the GitHub repository NYTC69/review-loop (3 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 684 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
codex-collaboration
Delegate to Codex AI when you need alternative implementation approaches, code analysis from a different perspective, or want to explore multiple solutions. Best for complex coding tasks that benefit from a second AI opinion.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.