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 skills/tomkrikorian/visionosagents/coding-standards-enforcernpx skills add tomkrikorian/visionOSAgents --skill coding-standards-enforcergit clone --depth 1 https://github.com/tomkrikorian/visionOSAgentsWrote 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/skills/tomkrikorian/visionosagents/coding-standards-enforcer)<a href="https://agentmods.dev/skills/tomkrikorian/visionosagents/coding-standards-enforcer"><img src="https://agentmods.dev/badge/skills/tomkrikorian/visionosagents/coding-standards-enforcer.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.00068 | $0.00868 |
| Opus 5 | $0.00034 | $0.00434 |
| Sonnet 5 | $0.00014 | $0.00174 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
coding-standards-enforcer 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards Enforcer
Quick Start
Use this skill whenever Swift source changes are in scope and the question is whether the code matches the repository's concurrency, observation, and modern API standards.
- Classify the work first:
- Swift 6.2 build-setting / language-mode problem
- Swift
MainActor/ actor isolation /Sendableproblem - Observation
@Observable/ SwiftUI@State/@Bindableownership problem - modern API / style / safety cleanup
- Load only the reference files that match that category.
- Review the changed code in this order:
- compiler diagnostics and isolation boundaries
- ownership and observation model
- API modernization and safety
- Fix or flag deviations explicitly; do not leave standards violations implied.
Load References When
| Reference | When to Use |
|---|---|
references/standards-review-map.md |
When you need the review order, routing, and repo-level standards map. |
references/concurrency-guidelines.md |
When the work touches actors, @MainActor, Sendable, Task, async let, task groups, or strict concurrency diagnostics. |
references/observation-modeling.md |
When the work touches Observation @Observable, @ObservationIgnored, SwiftUI @State, @Bindable, @Binding, or typed environment data flow. |
references/modern-swift-apis.md |
When the work is about API modernization, Foundation replacements, formatting, string matching, force unwraps, or Swift-native style. |
Workflow
- Inspect the changed Swift files and note the primary failure class.
- Load the narrowest relevant reference file or files.
- Apply the minimum change that restores compliance.
- Rebuild or rerun the affected test scope if available.
- Summarize what was fixed, what was intentionally left alone, and any remaining migration debt.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 79 lines · 68 tokens per session scan A 56e25761abae
coding-standards-enforcer is a skill published in the GitHub repository tomkrikorian/visionOSAgents (60 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 868 once invoked, about $0.0003 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.
Other skills, from other repositories
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
gradle-expert
Build optimization, dependency resolution, and multi-module KMP troubleshooting for AmethystMultiplatform. Use when working with: (1) Gradle build files (build.gradle.kts, settings.gradle), (2) Version catalog (libs.versions.toml), (3) Build errors and dependency conflicts, (4) Module dependencies and source sets, (5)…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
developing-genkit-dart
Generates code and provides documentation for the Genkit Dart SDK. Use when the user asks to build AI agents in Dart, use Genkit flows, or integrate LLMs into Dart/Flutter applications.
wax
Swift framework guidance for Wax on-device memory/RAG. Use when writing Swift code with the public Memory facade, experimental PhotoMemory / VideoMemory, BuiltInMultimodalEmbeddings, embedding providers, retrieval modes, or hybrid search. For agent operators using the Wax MCP server tools, use the separate wax-mcp…