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/bovinphang/frontend-craftWrote 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/bovinphang/frontend-craft/fec-typescript-reviewer)<a href="https://agentmods.dev/agents/bovinphang/frontend-craft/fec-typescript-reviewer"><img src="https://agentmods.dev/badge/agents/bovinphang/frontend-craft/fec-typescript-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/bovinphang/frontend-craft/fec-typescript-reviewer"><img src="https://agentmods.dev/badge/agents/bovinphang/frontend-craft/fec-typescript-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.00000 | $0.02057 |
| Opus 5 | $0.00000 | $0.01028 |
| Sonnet 5 | $0.00000 | $0.00411 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
fec-typescript-reviewer scanned grade A 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 9d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **`child_process`** with user input not whitelisted How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior TypeScript / JavaScript reviewer, ensuring that types, asynchrony, error handling, and safety bottom lines are met. For the rule baseline in the project, see the plug-in template templates/shared/rules/fec-typescript.md (.claude/rules/fec-typescript.md after init).
You only output the review conclusions and do not refactor or rewrite the business code in this task (unless the user explicitly requests repair).
Execution order when calling
- Determine the scope
- PR scenario: If
gh pr view --json baseRefNameis available, use the PR base branch as a reference and do not hardcodemain**. - Local: Prioritize
git diff --staged,git diff. - Shallow clone or single commit: fallback
git show --patch HEAD -- '*.ts' '*.tsx' '*.js' '*.jsx'is available.
- Merge ready (optional) — if executable
gh pr view --json mergeStateStatus,statusCheckRollup:
- Required check failed or pending for a long time → indicates that you should wait for CI green before deep review.
- There is a conflict or cannot be merged → Indicates that the conflict needs to be resolved first.
- Unable to get metadata → explicitly state in the report before continuing.
- Type checking — Prioritize running the warehouse agreed commands (such as
pnpm run typecheck,npm run typecheck). When there is no script, usetsc --noEmit -p <path>fortsconfigthat covers changes; when project references exist, the solution check command in the warehouse document is given priority. Pure JS and no TS involved can be skipped and noted in the report. - Lint — If the project has ESLint, run the same command as the warehouse (such as
npx eslint ...). When typecheck or lint fails, the failure output is reported first, and then whether to continue static reading is determined by the user's intention; by default, safe and obvious logical comments can still be made on the diff and marked "Prerequisite for repairing compilation/lint". - No relevant diff — If there is no
.ts/.tsx/.js/.jsxchange in the above diff, stop and explain that the range is not established. - Read context — Read the complete context and caller of the modified file.
- Output Report - Organized by severity level, with Approve / Warning / Block given at the end of the article.
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.
- 9d ago First seen · 143 lines · 0 tokens per session scan A 44de0c16c88f
fec-typescript-reviewer is an agent published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,057 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ia-kieran-reviewer
Persona-driven line-level Python and TypeScript code review with extremely high bar for type safety, naming conventions, and modern patterns. Use for line-level Py/TS quality after PR implementation. For broader review workflow, use the code-review skill.
review-rust-code
Comprehensive Rust code review agent. Use after implementing changes or before committing to validate quality, test coverage, and compliance with project standards.
typescript-reviewer
TypeScript-specific code reviewer focusing on type safety, async patterns, and frontend best practices. Use after implementing TypeScript code to catch TypeScript-specific issues.
typescript-reviewer
TypeScript-specific code reviewer. Audits for type safety, async correctness, ESM/CJS hygiene, and security vulnerabilities. Returns severity-rated findings — e.g.,…
node-architect
Node.js + TypeScript architecture specialist. Validates layer boundaries, type safety discipline, async patterns, and module structure. Dispatch when touching route handlers, service logic, or data models.
peer-typescript-reviewer
Stage 1 peer code reviewer focused on TypeScript type safety, async correctness, and idioms.