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 skills add Abdullah4AI/apple-developer-toolkit --skill repositoriesgit clone --depth 1 https://github.com/Abdullah4AI/apple-developer-toolkitWrote 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/abdullah4ai/apple-developer-toolkit/repositories)<a href="https://agentmods.dev/skills/abdullah4ai/apple-developer-toolkit/repositories"><img src="https://agentmods.dev/badge/skills/abdullah4ai/apple-developer-toolkit/repositories.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00627 |
| Opus 5 | $0.00015 | $0.00313 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
repositories 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Pattern
Architecture Overview
The repository pattern separates data access from business logic. ViewModels depend on protocol abstractions — never concrete implementations or database types.
Data flow: Supabase API → DTO (Codable) → Repository (maps) → Domain Model → ViewModel → View
Core Concepts
Repository Protocols
- Define async/throws methods returning domain models
- Live in
Repositories/{Entity}/{Entity}Repository.swift(e.g.Repositories/Users/UserRepository.swift) - One protocol per entity (UserRepository, PostRepository)
DTOs (Data Transfer Objects)
- Match database schema exactly (snake_case, Codable-friendly types)
- Live INSIDE concrete repository files — never exposed outside
- Separate insert DTOs omit auto-generated fields (id, created_at)
Domain Models
- Live in
Models/— use Swift-native types (enums, URL, Date) - Conform to
Identifiable(NOTCodable— they don't need serialization) - Include
static let samplefor SwiftUI previews
Concrete Implementations
- Live in
Repositories/{Entity}/Supabase{Entity}Repository.swift(e.g.Repositories/Users/SupabaseUserRepository.swift) - Contain: DTO struct, insert DTO,
init(dto:)mapping extension, implementation - Use
SupabaseService.shared.clientfor all database calls
Strict Rules
- ViewModels use protocols only — never
SupabaseUserRepository, alwaysUserRepository - DTOs never leak — no DTO type appears in protocol signatures, ViewModels, or Views
- Protocol methods return domain models —
func getAll() async throws -> [User] - Create methods take individual parameters — not domain models (ID is auto-generated)
- DI via init injection — concrete types only appear in App entry point (composition root)
Composition Root
The @main App struct is the only place that creates concrete repository instances and passes them down:
@main
struct MyApp: App {
var body: some Scene {
WindowGroup {
let userRepo = SupabaseUserRepository()
ContentView(viewModel: UserListViewModel(userRepository: userRepo))
}
}
}
What ships with it
2 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.
- 4d ago First seen · 69 lines · 29 tokens per session scan A 299e7f4042bb
repositories is a skill published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 627 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-09-03.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…