js-fp-review

A JavaScript and TypeScript code-review agent that checks for changes to arrays or function inputs, shared state, hidden side effects, and certain composition patterns.

In plain words
What is it for?
It is for reviewing JavaScript and TypeScript files, reporting mutation and side-effect problems, and suggesting clearer functional-style patterns.
Why use it?
It helps reveal code that changes data unexpectedly or hides actions inside calculations, which can make behavior harder to understand and maintain.

Agent

Install

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.

agentmods
npx agentmods add agents/bdfinst/agentic-dev-team/js-fp-review
Clone the repo
git clone --depth 1 https://github.com/bdfinst/agentic-dev-team
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,653 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.01653
Opus 5 $0.00015 $0.00826
Sonnet 5 $0.00006 $0.00331
Haiku 4.5 $0.00003 $0.00165

Measured 3d ago against content hash 784b0092dc61, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

js-fp-review 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 3d 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.

plugins/dev-team/agents/js-fp-review.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JS FP Review

Scope:

  • **/*.js
  • **/*.ts
  • **/*.jsx
  • **/*.tsx
  • **/*.mjs
  • **/*.cjs Cites: [adversarial-review-protocol]

Scope: JavaScript and TypeScript files only (.js, .ts, .jsx, .tsx, .mjs, .cjs). Skip this agent entirely if the project has no JS/TS files.

Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).

Status: pass=no mutations or impure patterns, warn=only style/point-free suggestions, fail=external mutation or a buried side effect Severity: error=external state mutation or a side effect buried inside a value-returning computation, warning=local mutation, suggestion=style (point-free/composition) Confidence: high=mechanical substitution (push→spread, let→const); medium=pattern clear but spread vs clone depends on usage, or extracting a console/DOM side effect; none=requires human judgment (intentional mutation for performance, or removing a non-deterministic read whose value is actually used downstream)

Context needs: diff-only

Skip

Return {"status": "skip", "issues": [], "summary": "No JS/TS files in target"} when:

  • No .js, .ts, .jsx, .tsx, .mjs, or .cjs files exist in the target
  • All target files are non-JavaScript/TypeScript

Detect

Variable declarations:

  • let never reassigned → use const
  • var → use const/let
  • Exception: prefixes mut/mutable/_ indicate intentional mutability

Array mutations (flag and suggest):

  • .push()[...arr, item]
  • .pop()arr.slice(0, -1)
  • .shift()arr.slice(1)
  • .unshift()[item, ...arr]
  • .splice() → slice + spread
  • .reverse()[...arr].reverse() or toReversed()
  • .sort()[...arr].sort() or toSorted()
  • .fill() → map
  • Exception: mutations on spread copies [...arr].sort() allowed

Object mutations:

  • param.prop = value (parameter mutation)
  • param[key] = value (parameter mutation)
  • delete param.prop
  • Object.assign(existingObj, ...) → spread or new object target
  • Exception: this.property in class methods allowed

Read the full file on GitHub · 106 lines

Changes

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.

  1. 3d ago First seen · 106 lines · 29 tokens per session scan A 784b0092dc61

Subscribe to this mod's changes

js-fp-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,653 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-30.