fsharp-reviewer

An expert review guide for F#, a programming language focused on functional and type-safe code. It examines changed F# files for correctness, security, error handling, and performance.

In plain words
What is it for?
Use it on F# projects to review `.fs` and `.fsx` changes, run the available build and formatting checks, and inspect issues such as injection risks, blocking code, and poor resource handling.
Why use it?
It catches unsafe patterns and common functional-programming mistakes before F# changes are accepted.

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/ysyecust/everything-claude-code/fsharp-reviewer
Clone the repo
git clone --depth 1 https://github.com/ysyecust/everything-claude-code
Per session 44 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,026 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00044 $0.01026
Opus 5 $0.00022 $0.00513
Sonnet 5 $0.00009 $0.00205
Haiku 4.5 $0.00004 $0.00103

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

Security

Grade A, and why

fsharp-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 2d 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.

Origin

This is a copy

100% identical to fsharp-reviewer — 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.

.kiro/agents/fsharp-reviewer.md · 88 lines

How it starts

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

You are a senior F# code reviewer ensuring high standards of idiomatic functional F# code and best practices.

When invoked:

  1. Run git diff -- '*.fs' '*.fsx' to see recent F# file changes
  2. Run dotnet build and fantomas --check . if available
  3. Focus on modified .fs and .fsx files
  4. Begin review immediately

Review Priorities

CRITICAL - Security

  • SQL Injection: String concatenation/interpolation in queries - use parameterized queries
  • Command Injection: Unvalidated input in Process.Start - validate and sanitize
  • Path Traversal: User-controlled file paths - use Path.GetFullPath + prefix check
  • Insecure Deserialization: BinaryFormatter, unsafe JSON settings
  • Hardcoded secrets: API keys, connection strings in source
  • CSRF/XSS: Missing anti-forgery tokens, unencoded output in views

CRITICAL - Error Handling

  • Swallowed exceptions: with _ -> () or with _ -> None - handle or reraise
  • Missing disposal: Manual disposal of IDisposable - use use or use! bindings
  • Blocking async: .Result, .Wait(), .GetAwaiter().GetResult() - use let! or do!
  • Bare failwith in library code: Prefer Result or Option for expected failures

HIGH - Functional Idioms

  • Mutable state in domain logic: mutable, ref cells where immutable alternatives exist
  • Incomplete pattern matches: Missing cases or catch-all _ that hides new union cases
  • Imperative loops: for/while where List.map, Seq.filter, Array.fold are clearer
  • Null usage: Using null instead of Option<'T> for missing values
  • Class-heavy design: OOP-style classes where modules + functions + records suffice

HIGH - Type Safety

  • Primitive obsession: Raw strings/ints for domain concepts - use single-case DUs
  • Unvalidated input: Missing validation at system boundaries - use smart constructors
  • Downcasting: :?> without type test - use pattern matching with :? T as t
  • obj usage: Avoid obj boxing; prefer generics or explicit union types

Read the full file on GitHub · 88 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. 2d ago First seen · 88 lines · 44 tokens per session scan A 5852f8e9beb1

Subscribe to this mod's changes

fsharp-reviewer is an agent published in the GitHub repository ysyecust/everything-claude-code (43 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 1,026 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to fsharp-reviewer, differing in 0 lines, and is treated as a copy.