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/mathisk2095/jko-claude-pluginsWrote 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/commands/mathisk2095/jko-claude-plugins/swift-critique)<a href="https://agentmods.dev/commands/mathisk2095/jko-claude-plugins/swift-critique"><img src="https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/swift-critique/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/commands/mathisk2095/jko-claude-plugins/swift-critique"><img src="https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/swift-critique.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.00017 | $0.01245 |
| Opus 5.5 | $0.00007 | $0.00498 |
| Sonnet 5.5 | $0.00003 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
swift-critique 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUI Critique
Load the swiftui-expert skill for reference knowledge, then perform a grounded critique of SwiftUI code.
Gather Context First
Before flagging anything, understand the project:
- Check deployment target from
Package.swift,*.xcodeproj/project.pbxproj, or*.xcconfigfiles - Check if the project uses
@ObservableorObservableObject(don't flagObservableObjectif the whole project consistently uses it and targets < iOS 17) - Check if the project has a design system / theme (shared colors, fonts, spacing constants)
- Note any architectural patterns already in use (MVVM, MV, coordinator, etc.)
What to Critique
If $ARGUMENTS specifies a file or directory, critique that. If no arguments, find Swift files in the current project:
- Use Glob to find
**/*.swiftfiles - Use Read to examine each SwiftUI file (files importing SwiftUI or containing
Viewconformances) - Skip non-SwiftUI files (pure model/utility code without UI)
Critique Rules
- Read the actual code before flagging. Do not flag something you haven't verified by reading the file.
- Respect project conventions. If the project consistently uses a pattern (e.g.,
ObservableObject, computed view properties), don't flag every instance — note it once as a project-wide suggestion. - Verify before flagging. If you think something is unused or misused, check the call sites. An
@Environmentproperty added in the same session may be used in code you haven't read yet. - No generic advice. Every finding must reference a specific file and line number with actual code from the project.
Critique Process
Review each file against these categories in order:
1. Deprecated API
- Flag any deprecated API usage (foregroundColor, NavigationView, ObservableObject, etc.)
- Show the modern replacement with before/after code
2. State & Data Flow
- Verify
@Stateisprivate(skip if the project has a pattern of non-private@Statefor parent injection) - Check
@Observableclasses are@MainActor(only if project targets iOS 17+) - Flag
Binding(get:set:)in body - Flag
@AppStorageinside@Observable - Check for broad observation dependencies (verify by reading the model, not guessing)
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.
- 1mo ago First seen · 125 lines · 17 tokens per session scan A ba0061a1def8
swift-critique is a command published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 10d ago), licensed MIT. It adds 17 tokens to every session and 1,245 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.
compliance-fix
Show Qualimetry review findings for a file and apply the standards-compliant fix.
review
Command "review" from KhaiTrang1995/claude-code-structure, covering /project:review – code review command, usage, description, output format and shell step.