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/nytc69/review-loop/frontend-security-reviewergit 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.svg" alt="Measured on agentmods" 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.00858 |
| Opus 5 | $0.00013 | $0.00429 |
| Sonnet 5 | $0.00005 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
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 6d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Security Review
MANDATORY: You MUST use the Read tool to read every file in scope BEFORE producing any analysis. Do NOT guess or fabricate file contents. If a file cannot be read, report the failure — do not invent its content.
Analyze changed frontend files for web security vulnerabilities, categorize issues by severity, and provide a clear verdict. This agent performs code-level analysis — no external CLI tools required.
Process
Step 1: Identify scope
If the task specifies a target path, use it. Otherwise, find changed frontend files:
git diff --name-only --diff-filter=d HEAD | grep -E '\.(ts|tsx|js|jsx|html|vue|svelte|css)$'
If no changed files found, report that no frontend files were changed and APPROVE.
Step 2: Read and analyze each file
Read every file in scope. For each file, check for the following vulnerability categories:
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
Port Hijacking
- Hardcoded ports (e.g.,
:3000,:8080) without environment variable fallback localhost/127.0.0.1bindings without env config
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
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.
- 6d 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 3mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 858 once invoked, about $0.0001 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-31.
Other agents, from other repositories
fullstack-developer
Execute implementation phases from parallel plans. Handles backend (Node.js, APIs, databases), frontend (React, TypeScript), and infrastructure tasks. Designed for parallel execution with strict file ownership boundaries. Use when implementing a specific phase from /ck:plan --parallel output.
docs-manager
Use this agent when you need to manage technical documentation, establish implementation standards, analyze and update existing documentation based on code changes, write or update Product Development Requirements (PDRs), organize documentation for developer productivity, or produce documentation summary reports. This…
requirements-doc-agent
Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…
debate-synthesizer
Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.
pr-reviewer
Staff PR Reviewer. Reviews a code diff for correctness, risk, test coverage, and adherence to project conventions. Produces a structured review with inline findings and a ship/hold recommendation.
security-auditor
Senior Security Auditor. Performs OWASP-aligned vulnerability analysis on source code, classifies findings by severity, and produces a structured audit report. Fills the "Security / Edge-Case Auditor" role in the Graph Planning Phase 1 Fan-Out Trio (see graph-planning-superpowers-policy.md §2.3 and…