SwiftUIBackports is a Swift package that recreates selected newer SwiftUI APIs for older versions of Apple’s operating systems, using familiar names and behavior where practical. Swift developers use it to adopt newer interface patterns while keeping applications compatible with earlier iOS, macOS, tvOS, and watchOS releases. The catalogue entries include agents, instructions, and a discovery skill that help coding agents locate and use the available backports.
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/shaps80/swiftuibackports/agents-mdgit clone --depth 1 https://github.com/shaps80/SwiftUIBackportsWrote 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/instructions/shaps80/swiftuibackports/agents-md)<a href="https://agentmods.dev/instructions/shaps80/swiftuibackports/agents-md"><img src="https://agentmods.dev/badge/instructions/shaps80/swiftuibackports/agents-md.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.00653 | $0.00653 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
SwiftUIBackports 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 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
When talking to the user, sacrifice grammar for concision.
First Reads
Before code work, read CONTEXT.md. It defines project terms, API-shape expectations, availability rules, and release policy. If an ADR exists under docs/adr/ for the area you touch, read it too.
When implementing a SwiftUI API backport, check refs/swiftui-*.ref and refs/swiftuicore-*.ref for Xcode SwiftUI/SwiftUICore module interface references. Use the newest versioned refs to confirm native signatures, overload sets, generics, availability, and hidden helper types before shaping public API.
If the available SwiftUI max version is newer than the newest ref version in refs/, tell the user the ref files may need updating before relying on them.
Project Rules
- This is a SwiftPM library, not an app.
- Main target is
SwiftUIBackports. - Preserve Apple SwiftUI API parity for backports: names, overloads, behavior, docs, and availability should match native APIs where practical.
- Use the refs to discover official API introduction versions. Backport APIs should be deprecated on each platform at the version where the native API was introduced for that platform. Example: if
presentationBackgroundInteractionis officially introduced on iOS 16.3, the iOS deprecation for the backport should be 16.3. - When a full SwiftUI type is backported, usually put native-availability deprecation on the backported type itself, not every initializer, method, or extension on that type. Add member-level deprecations only when needed, such as a member whose native API was introduced in a different version. This does not apply to modifiers, environment values, or other non-type API backports.
- Prefer
.backportmodifiers for view/transition APIs andBackport<Any>for pure namespace types. - Keep UIKit/AppKit bridge details internal/private unless public API parity demands exposure.
- Use
@availableand#if os(...)deliberately. Minimum floors are iOS 13, tvOS 13, watchOS 6, macOS 10.15. - Do not move deprecated APIs casually. Deprecation shims are source-compatibility promises.
- PRs need exactly one release label:
release:majororrelease:minor.
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 · 45 lines · 653 tokens per session scan A bf69a83c5ae7
SwiftUIBackports AGENTS.md is an instructions file published in the GitHub repository shaps80/SwiftUIBackports (1,089 stars, last pushed 2mo ago), licensed MIT. It adds 653 tokens to every session, about $0.0033 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 instructions, from other repositories
MarkdownView AGENTS.md
Instructions for keitaoouchi/MarkdownView, covering agents, technical components, relationships (data/event flow overview), extension points (overview) and platform / distribution.
SwiftUIShaders AGENTS.md
Instructions for krispuckett/SwiftUIShaders, covering agents.md: architecture for coding agents, what this package is, how swiftui metal shader effects work (the mental model), how to add a new shader and how to modify an existing shader.
hermex AGENTS.md
AGENTS.md instructions for uzairansaruzi/hermex, covering hermex, what makes hermex special?, 1. open at the core, 2. performance without compromise and 3. remote ready.
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.
swiftui-native-component-design-skill AGENTS.md
Instructions for alexanderwe/swiftui-native-component-design-skill, covering agent guidelines for swiftui native component design skill, core principles, 1. component api design only, 2. no architectural mandates and 3. templates are adaptable, not literal.
everything-claude-code-mobile copilot-instructions.md
Copilot instructions for ahmed3elshaer/everything-claude-code-mobile: Use this repository's mobile guidance for Android, iOS, and Kotlin Multiplatform work.