Borrowing it
Nothing to install: this file belongs to Erikote04/Swift-API-Design-Guidelines-Agent-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/Erikote04/Swift-API-Design-Guidelines-Agent-Skill/main/AGENTS.mdgit clone --depth 1 https://github.com/Erikote04/Swift-API-Design-Guidelines-Agent-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/erikote04/swift-api-design-guidelines-agent-skill/agents-md)<a href="https://agentmods.dev/instructions/erikote04/swift-api-design-guidelines-agent-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/erikote04/swift-api-design-guidelines-agent-skill/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/erikote04/swift-api-design-guidelines-agent-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/erikote04/swift-api-design-guidelines-agent-skill/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00494 | $0.00494 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
Swift-API-Design-Guidelines-Agent-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 9d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Design Guidelines Skill Authoring Guide
Core Principles
- Optimize for clarity at the point of use.
- Treat clarity as more important than brevity.
- Keep instructions factual, specific, and testable in code review.
- Prefer Swift-native idioms over personal style preferences.
- Keep the skill focused on API design, naming, labels, and documentation quality.
Content Guidelines
- Keep
SKILL.mdprocedural and concise. - Put detailed rule explanations and examples in
references/. - Organize content by decision points the agent can apply while reviewing or writing code.
- Use concrete "good vs bad" examples for naming and labels.
- Avoid duplicating the same rule in multiple files unless needed for quick-reference context.
What To Include
- Swift API naming rules and argument-label guidance.
- Documentation comment rules and symbol-markup usage.
- Mutating/nonmutating naming pairs and side-effect naming patterns.
- Conventions for terminology, casing, overload design, and default parameters.
- Review checklists and action-oriented guidance for code changes.
What To Exclude
- App architecture prescriptions (MVVM/VIPER/etc.).
- Style debates unrelated to API surface design.
- Language features not relevant to API clarity.
- Long historical commentary or rationale not needed for implementation decisions.
- Duplicate reference material across multiple files.
Language And Tone
- Use direct, technical language.
- Use imperative instructions for actionable rules.
- Prefer short paragraphs and bullet lists over prose-heavy explanations.
- Keep examples compact and realistic.
- Avoid motivational or opinionated language.
Examples
- Include paired examples where possible:
- Ambiguous vs clear API names.
- Redundant vs concise naming.
- Incorrect vs correct argument labels.
- Overload ambiguity vs explicit method naming.
- Prefer examples that reveal point-of-use readability, not declaration-only quality.
Updating The Skill
- Update
SKILL.mdfirst when workflow or review process changes. - Update only the affected
references/*.mdfiles when a rule changes. - Preserve section structure so other agents can find guidance predictably.
- Keep
references/filenames stable; add new files only for genuinely new topics. - Validate checklists against the references after each update.
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.
- 9d ago First seen · 55 lines · 494 tokens per session scan A a81021e1a1e5
Swift-API-Design-Guidelines-Agent-Skill AGENTS.md is an instructions file published in the GitHub repository Erikote04/Swift-API-Design-Guidelines-Agent-Skill (29 stars, last pushed 6mo ago), licensed MIT. It adds 494 tokens to every session, about $0.0025 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
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.