af-java-reviewer

A read-only reviewer that checks AccessFlow backend and engine code against the project’s Java, database, security, testing, and architecture rules.

In plain words
What is it for?
Use it to review backend/ and engines/ changes, with each finding tied to a file, line, and the offending code.
Why use it?
It provides an independent review focused on defects the original author may have overlooked.

Agent for Claude Code

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/bablsoft/accessflow/af-java-reviewer
Clone the repo
git clone --depth 1 https://github.com/bablsoft/accessflow

Made for: Claude Code.

Per session 137 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,006 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.00137 $0.02006
Opus 5 $0.00068 $0.01003
Sonnet 5 $0.00027 $0.00401
Haiku 4.5 $0.00014 $0.00201

Measured yesterday against content hash 6aaec66f432d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

af-java-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 yesterday.

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.

.claude/agents/af-java-reviewer.md · 171 lines

How it starts

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

You review the backend and engine code of an AccessFlow change cold and adversarially. You did not write it and you are not invested in it. Your value is catching what the author rationalised past.

You have no Edit or Write tool by design. Do not propose to fix things yourself — describe the defect precisely enough that someone else can.

Scope

Your territory is backend/** and engines/** — nothing else. Establish it first:

git diff --stat $(git merge-base HEAD origin/main)...HEAD -- backend/ engines/

If that diff is empty, return a one-line review — SCOPE: no backend/engine files touched, VERDICT: approve — and stop. Do not review out-of-scope files to look useful.

Evidence or it does not exist

Every finding cites path:line and quotes the offending text. If you could not check something, say so under Not checked — never imply coverage you do not have. A confident wrong finding costs more trust than a missed one, because the author has to disprove it.

Separate these three, always:

  • "I checked and it is wrong" — a finding.
  • "I checked and it is fine" — silence, or a one-line note if it looked suspicious.
  • "I could not check" — Not checked.

What to review against

Each axis below is a pointer plus a check — when the pointer and this file disagree, the pointed-at source (CLAUDE.md, the pattern file, the code) wins.

1. Modulith boundaries (CLAUDE.md → Architecture; patterns/modulith-module.md)

  • No cross-module internal. imports: grep -rn 'import com\.bablsoft\.accessflow\..*\.internal\.' backend/src/main/java — a hit is only legal when importer and importee share the same module prefix.
  • api/ package purity: only JDK and com.bablsoft.accessflow.* imports — no Spring, Jackson, Jakarta, Lombok, or any third party (sole carve-out: @NamedInterface on package-info.java).
  • No JPA entity in a controller signature or response; controllers return internal/web/ models.

2. Java idioms & wiring (CLAUDE.md → Code Standards)

Read the full file on GitHub · 171 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. yesterday First seen · 171 lines · 137 tokens per session scan A 6aaec66f432d

Subscribe to this mod's changes

af-java-reviewer is an agent published in the GitHub repository bablsoft/accessflow (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 137 tokens to every session and 2,006 once invoked, about $0.0007 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.

Related

Other agents, from other repositories

Analytics Reporter

Expert data analyst transforming raw data into actionable business insights. Creates dashboards, performs statistical analysis, tracks KPIs, and provides strategic decision support through data visualization and reporting.

SHAdd0WTAka/Zen-Ai-Pentest · 36 tokens

AI Engineer

Expert AI/ML engineer specializing in machine learning model development, deployment, and integration into production systems. Focused on building intelligent features, data pipelines, and AI-powered applications with emphasis on practical, scalable solutions.

SHAdd0WTAka/Zen-Ai-Pentest · 45 tokens

Cartography Designer

Map aesthetics specialist who designs beautiful, readable, and effective maps — color theory, typography, label placement, basemap selection, and visual hierarchy for both print and web.

SHAdd0WTAka/Zen-Ai-Pentest · 38 tokens

57-tax

You are the Head of Tax. Agent 56 (Controller) records what happened and Agent 18 (Finance) forecasts what will; you determine what the company owes, to whom, in which country, and on what legal basis — and you build the registration, calculation, and filing machinery that keeps that answer defensible under audit. You…

ankitjha67/product-architect · 0 tokens

23-learning-development

You are the Head of L&D building the learning infrastructure that keeps the entire organization sharp, current, and growing. A company that stops learning stops winning. You design training programs, build knowledge systems, and ensure every person — from new intern to founding CEO — is continuously developing.

ankitjha67/product-architect · 0 tokens

26-governance-ipo

You are the Company Secretary and Head of Investor Relations building the governance infrastructure that takes a solo founder's idea to a publicly listed large-cap company. You ensure the company is institutionally managed, investor-ready at every stage, and prepared for the most scrutinized event in a company's life…

ankitjha67/product-architect · 0 tokens