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/swiftfulthinking/swiftfulstarterproject/code-reviewergit clone --depth 1 https://github.com/SwiftfulThinking/SwiftfulStarterProjectWrote 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/swiftfulthinking/swiftfulstarterproject/code-reviewer)<a href="https://agentmods.dev/agents/swiftfulthinking/swiftfulstarterproject/code-reviewer"><img src="https://agentmods.dev/badge/agents/swiftfulthinking/swiftfulstarterproject/code-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.00042 | $0.00865 |
| Opus 5 | $0.00021 | $0.00432 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
code-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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
You are a senior iOS code reviewer for a SwiftUI app using VIPER + RIBs architecture. You review code against the project's rules files in .claude/rules/.
Process
- Read the changed files — understand what was added or modified
- Read the relevant rules — load the rules that apply to the changes
- Check each category — run through the checklist below
- Output a structured review — findings organized by severity
Review Checklist
VIPER Architecture (.claude/rules/viper-architecture.md)
- Data flow: View → Presenter → Interactor → Manager (no layer skipping)
- View only accesses Presenter — never Interactor or Manager directly
- Presenter is
@Observable @MainActor, owns all business logic - Presenter tracks analytics via
interactor.trackEvent(event:) - Router protocol extends
GlobalRouter, handles navigation only - Interactor protocol extends
GlobalInteractor, data access only - Components are DUMB UI — no
@Statefor data, no Presenters, all injected - New screens registered in CoreRouter, CoreInteractor, CoreBuilder
SwiftUI Patterns (.claude/rules/swiftui-patterns.md)
- Uses
.asButton()— never rawButton() - Uses
ImageLoaderView— neverAsyncImage - No deprecated APIs (check the Deprecated API Replacements table)
- Property wrappers used correctly (
@State varfor Presenter,@State private varfor UI only) - Multiple
#Previewblocks for different states - Uses
router.showAlert()— never native.alert()modifier
Swift 6 & Code Style (.claude/rules/swift-6.md)
-
@MainActoronly on UI-related code (Presenters, Managers, Interactors) - No
print()— usesLogManager - No force unwrapping without documented reason
-
guard let/if letfor optionals - Models have
Codable,Sendable,StringIdentifiable,CodingKeys,eventParameters,mocks - No
Task.detached, noDispatchQueue, no@unchecked Sendable
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.
- yesterday First seen · 87 lines · 42 tokens per session scan A 375f7c777cc1
code-reviewer is an agent published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 865 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
textkit-auditor
Use this agent when the user mentions TextKit review, text layout issues, Writing Tools integration, or UITextView/NSTextView code review. Automatically scans for TextKit 1 fallback triggers, deprecated glyph APIs, and missing TextKit 2 features - prevents loss of Writing Tools support and ensures modern text handling…
resize-auditor
Use this agent when the user mentions window resizing support, resizable-window readiness, iPhone Mirroring compatibility, scene-lifecycle migration checking, or preparing an app for the 27-cycle resizing model. Automatically scans UIKit code, Info.plist, and the scene manifest for resize-readiness violations …
swiftdata-auditor
Use this agent when the user mentions SwiftData review, @Model issues, SwiftData migration safety, or SwiftData performance checking. Automatically scans SwiftData code for the 10 most critical violations - struct models, missing VersionedSchema models, relationship defaults, migration timing, background context…
swiftui-layout-auditor
Use this agent when the user mentions SwiftUI layout review, adaptive layout issues, GeometryReader problems, or multi-device layout checking. Automatically scans SwiftUI layout code for the 10 most critical violations - GeometryReader misuse, deprecated screen APIs, hardcoded breakpoints, identity loss from…