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 instructions/efremidze/swift-patterns-skill/agents-mdgit clone --depth 1 https://github.com/efremidze/swift-patterns-skillWhat 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.01145 | $0.01145 |
| Opus 5 | $0.00573 | $0.00573 |
| Sonnet 5 | $0.00229 | $0.00229 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
swift-patterns-skill AGENTS.md 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 3d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines for Swift Patterns
This document provides guidance for AI agents working with this skill to ensure consistency and avoid common pitfalls.
Core Principles
1. Swift and SwiftUI Focus
This is a Swift and SwiftUI skill. Do not include:
- Server-side Swift patterns
- UIKit patterns (except when bridging is necessary)
- Deep Swift concurrency patterns (actors, Sendable, etc.) — use
.taskfor SwiftUI async work when needed
2. No Code Formatting or Linting
Do not include formatting/linting rules. Avoid:
- Property ordering requirements (environment, state, body, etc.)
- Code organization mandates
- Whitespace or indentation rules
- Naming convention enforcement
- File structure requirements
Exception: Mention organization patterns as optional suggestions for readability, never as requirements.
3. No Architectural Opinions
Stick to facts, not architectures. Avoid:
- Enforcing MVVM, MVC, VIPER, or any specific architecture
- Mandating view model patterns
- Requiring specific folder structures
- Dictating dependency injection patterns
- Prescribing router/coordinator patterns
Exception: Suggest separating business logic for testability without enforcing how.
4. No Tool-Specific Instructions
Agents cannot use external tools. Do not include:
- Xcode Instruments profiling instructions
- Debugging tool usage
- IDE-specific features
- Command-line tool usage beyond basic git
Exception: Mention that users can profile with Instruments if performance issues arise, but don't provide detailed instructions.
Content Guidelines
Suggestions vs Requirements
Use "suggest" or "consider" for optional optimizations:
- ✅ "Consider downsampling images when using
UIImage(data:)" - ❌ "Always downsample images"
Use "always" or "never" only for correctness issues:
- ✅ "Never use
.indicesfor dynamic ForEach content" - ✅ "Always mark
@Stateasprivate"
Performance Optimizations
Present performance optimizations as optional improvements:
- Image downsampling: Suggest when
UIImage(data:)is encountered - POD view wrappers: Mention as advanced optimization technique
- Equatable conformance: Suggest for expensive views
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.
- 3d ago First seen · 158 lines · 1,145 tokens per session scan A 1269ba617c30
swift-patterns-skill AGENTS.md is an instructions file published in the GitHub repository efremidze/swift-patterns-skill (9 stars, last pushed 5mo ago), licensed MIT. It adds 1,145 tokens to every session, about $0.0057 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-31.
Other instructions, from other repositories
swift-architecture-skill CLAUDE.md
Instructions for efremidze/swift-architecture-skill, covering swift architecture skill, project structure, how the skill works and key conventions.
swift-architecture-skill AGENTS.md
Instructions for efremidze/swift-architecture-skill, covering agents guidelines for swift architecture skill, working with this repository, 1. understanding the skill, 2. modifying architecture playbooks and 3. testing and validation.
ios-swiftui-accessibility-techniques CLAUDE.md
Instructions for cvs-health/ios-swiftui-accessibility-techniques, covering project rules, copyright header (required), rules, swift files and markdown files.
MarkdownView AGENTS.md
Instructions for keitaoouchi/MarkdownView, covering agents, technical components, relationships (data/event flow overview), extension points (overview) and platform / distribution.
swift-tui AGENTS.md
Instructions for SwiftTUI/swift-tui, covering agents.md, build & test commands, architecture (one-page summary), development guidelines and code style.
swiftui-compose-skill AGENTS.md
Instructions for sorunokoe/swiftui-compose-skill, covering agents.md — swiftui-compose, what this repository is, repository structure, how to apply this skill and reference selection guide.