Borrowing it
Nothing to install: this file belongs to jeremieb/swift-unit-test-instructions. 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/jeremieb/swift-unit-test-instructions/main/CLAUDE.mdgit clone --depth 1 https://github.com/jeremieb/swift-unit-test-instructionsWrote 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/jeremieb/swift-unit-test-instructions/claude-md)<a href="https://agentmods.dev/instructions/jeremieb/swift-unit-test-instructions/claude-md"><img src="https://agentmods.dev/badge/instructions/jeremieb/swift-unit-test-instructions/claude-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.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
swift-unit-test-instructions CLAUDE.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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Swift / SwiftUI / UIKit Project
Project Configuration
- Project Name: [MyApp]
- Testing Mode: [enterprise | indie]
- UI Framework: [SwiftUI | UIKit | Both]
- Min iOS Version: [17.0]
- Architecture: MVVM
Workflow
- Enter plan mode for any non-trivial task (3+ steps or architectural decisions)
- Never mark a task complete without running tests and verifying the build
- After any user correction: update
tasks/lessons.mdto prevent the same mistake - When given a bug: fix it autonomously — point at logs, errors, failing tests, then resolve
Core Principles
- Simplicity first. Minimal code impact. One thing at a time.
- Thin UI layers. Business logic never belongs in Views or ViewControllers.
- If something is hard to test, the architecture needs improvement — not the test.
Available Skills
Install in .claude/skills/ — they auto-trigger based on your request.
| Skill | Triggers on |
|---|---|
swift-project-setup |
"new project", "scaffold", "setup app" |
swift-testing |
"write tests", "add unit tests", "test this" |
swift-architecture-audit |
"audit codebase", "why is this untestable", "onboard" |
swiftui-component |
"create view", "add screen", "build UI" |
swift-networking |
"add networking", "create API layer" |
swift-persistence |
"add CoreData", "set up SwiftData", "persist data" |
swift-code-review |
"review this", "check this PR" |
Commands
Run with /command-name in Claude Code.
| Command | What it does |
|---|---|
/swift-feature |
Full feature workflow: analysis → confirm → implement → build |
/swift-build |
Build validation (xcodebuild or swift build) |
/swift-arch-check |
Read-only architecture audit with structured report |
Agents
Invoked by commands or directly by name.
| Agent | Role |
|---|---|
swift-staff-engineer |
Skeptical senior reviewer — finds issues before they ship |
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.
- 8d ago First seen · 61 lines · 517 tokens per session scan A 54854812bbb5
swift-unit-test-instructions CLAUDE.md is an instructions file published in the GitHub repository jeremieb/swift-unit-test-instructions (5 stars, last pushed 6mo ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 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
pudo-code-system pudo-tests.instructions.md
Instructions for DongDuong2001/pudo-code-system, covering test code guidelines, test structure, test coverage, test quality and verification.
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.