Borrowing it
Nothing to install: this file belongs to alexanderwe/swiftui-native-component-design-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alexanderwe/swiftui-native-component-design-skill/main/AGENTS.mdgit clone --depth 1 https://github.com/alexanderwe/swiftui-native-component-design-skillWrote 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/alexanderwe/swiftui-native-component-design-skill/agents-md)<a href="https://agentmods.dev/instructions/alexanderwe/swiftui-native-component-design-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/alexanderwe/swiftui-native-component-design-skill/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.1 | $0.01165 | $0.01165 |
| Opus 5 | $0.00583 | $0.00583 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
swiftui-native-component-design-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 6d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines for SwiftUI Native Component Design Skill
Guidance for AI agents working on this skill's content, to keep it consistent and avoid scope creep.
Core Principles
1. Component API design only
This skill is about the API surface of a reusable SwiftUI component: classification (semantic vs. prescriptive), semantic modeling, data-flow primitives (Binding vs. immutable input vs. @State), initializer shape, and the customization mechanism (ViewStyle vs. environment value). Do not expand it into:
- A general SwiftUI-patterns reference (state management internals, performance tuning, Liquid Glass, Swift Charts, navigation/list patterns) — that's a different skill's job
- Swift language features unrelated to component API shape
- Backend, networking, or persistence concerns
2. No architectural mandates
Don't enforce MVVM/MVC/VIPER, view-model requirements, or folder-structure conventions. The skill's five steps apply regardless of the surrounding app architecture.
3. Templates are adaptable, not literal
The reference files (initializers.md, view-styles.md, environment-customization.md) work through one concrete example each (Card/Tag, Rating/RatingStyle, Tag/tagBackgroundStyle). When applying the skill, the pattern (protocol shape, resolver-view structure, @Entry registration) is what transfers — names and concrete types should be renamed to fit whatever component is actually being designed. When editing the reference files themselves, keep them structured as one clear worked example rather than a menu of variations.
4. Classification drives everything downstream
Step 1 (semantic vs. prescriptive) is a fork in the road for Step 5 (customization API). Don't add guidance that lets a component skip classification and jump straight to picking a customization mechanism — that's the exact anti-pattern the skill exists to prevent (either over-building style-protocol machinery for something that will never need it, or under-building a fixed environment-only API for something that genuinely needs swappable visual representations).
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.
- 6d ago First seen · 90 lines · 1,165 tokens per session scan A 446356f5148b
swiftui-native-component-design-skill AGENTS.md is an instructions file published in the GitHub repository alexanderwe/swiftui-native-component-design-skill (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,165 tokens to every session, about $0.0058 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.