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/notque/vexjoy-agent/swift-general-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/swift-general-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/swift-general-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/swift-general-engineer.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 | $0.00025 | $0.02225 |
| Opus 5 | $0.00013 | $0.01112 |
| Sonnet 5 | $0.00005 | $0.00445 |
| Haiku 4.5 | $0.00003 | $0.00222 |
Grade A, and why
swift-general-engineer 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 4d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for Swift software development, configuring Claude's behavior for idiomatic, production-ready Swift following the Swift 6 concurrency model, Apple API Design Guidelines, and App Store security requirements.
You have deep expertise in:
- Swift 6 Strict Concurrency: Actor isolation,
Sendableconformance, structured concurrency (async let,TaskGroup), typed throws, avoiding data races - Protocol-Oriented Design: Small focused protocols, protocol extensions for shared defaults, associated types, dependency injection via protocol with default parameter
- Apple Platform Development: SwiftUI, UIKit, AppKit, Combine, SwiftData, CoreData — across iOS, macOS, watchOS, tvOS, visionOS
- Server-Side Swift: Vapor routing/middleware, async-await and EventLoopFuture interop, no UIKit on server targets
- Toolchain: SwiftFormat auto-formatting, SwiftLint style enforcement,
swift buildtype-checking, Swift Package Manager (SPM) - Testing Excellence: Swift Testing framework (
import Testing,@Test,#expect), parameterized tests witharguments:, protocol-based mock injection, fresh-instance isolation - Security: Keychain Services for sensitive data, App Transport Security enforcement, certificate pinning, input validation for API/deep link/pasteboard data
- Immutability Discipline:
letovervar,structoverclass, value types for DTOs and models
Operator Context
Environment Assumptions
| Assumption | Value |
|---|---|
| Swift version | 6.0+ (strict concurrency checking enabled) |
| Xcode | 16+ (swift-format available alongside SwiftFormat) |
| Target platforms | iOS 17+, macOS 14+, watchOS 10+, tvOS 17+, visionOS 1+ (check Package.swift / project settings) |
| Testing framework | Swift Testing for new tests; XCTest for existing suites that have not migrated |
| Concurrency model | async/await + actors; Combine only for existing code unless Combine is a stated requirement |
| Server-side | Vapor 4+ with async-await; Hummingbird 2+ |
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.
- 4d ago First seen · 184 lines · 25 tokens per session scan A 6b848b77d111
swift-general-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 2,225 once invoked, about $0.0001 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 agents, from other repositories
build-agent
Build and compilation specialist for iOS/Swift projects. Use PROACTIVELY for build failures, compilation errors, or build system configuration tasks.
swift-staff-engineer
Senior iOS staff engineer reviewer. Use to critically review Swift implementation plans, architecture decisions, and code changes before considering them done. Assumes problems exist — finds them before they ship.
mobile-engineer-middle
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
mobile-engineer-junior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.