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 skills add troyjthomas/ios-agent-skills --skill app-specgit clone --depth 1 https://github.com/troyjthomas/ios-agent-skillsWrote 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/skills/troyjthomas/ios-agent-skills/app-spec)<a href="https://agentmods.dev/skills/troyjthomas/ios-agent-skills/app-spec"><img src="https://agentmods.dev/badge/skills/troyjthomas/ios-agent-skills/app-spec/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/skills/troyjthomas/ios-agent-skills/app-spec"><img src="https://agentmods.dev/badge/skills/troyjthomas/ios-agent-skills/app-spec.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.00066 | $0.01169 |
| Opus 5.5 | $0.00026 | $0.00468 |
| Sonnet 5.5 | $0.00013 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
app-spec 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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Spec
Produce the two documents that govern your entire build. This still happens in Claude chat.
When to Use
- You've completed the app-vision skill
- You're ready to create the project repo
- You need a CLAUDE.md and app spec before touching Claude Code
Document 1: CLAUDE.md
This file lives in the root of your repo. Claude Code reads it automatically at the start of every session. It contains rules, not descriptions.
Required Sections
# [App Name] - Development Rules
## Core Principles
- Use native SwiftUI components exclusively unless explicitly told to build custom
- Target iOS [version]
- Follow Apple HIG for all spacing, typography, layout, and interaction patterns
- Use SF Symbols for all icons unless a custom asset is specified
- Use system fonts unless a specific typeface is called out
## Navigation
- [Tab-based / Single stack / Other] navigation pattern
- List every navigation path: what presents what, and how (push, sheet, menu)
- Define presentation rules:
- Sheets for: [creation, editing, multi-step flows]
- Menus for: [action lists, quick selections]
- Pickers for: [constrained value selection]
- Context menus for: [long-press actions on list items]
## Architecture
- SwiftUI + [SwiftData / Core Data / UserDefaults] for persistence
- [MVVM / other] pattern
- File structure conventions:
- /Components for shared components
- /Models for data models
- /Views/[Feature] for feature-specific views
## Color and Theming
- Primary tint: [hex or semantic description]
- Support light and dark mode from day one
- Use semantic colors (Color.primary, Color.secondary) for text
- [Liquid Glass / Material / other] treatment for system chrome
## Custom Components (the exceptions)
- List ONLY the components that cannot be built with native SwiftUI
- Each one gets a name and a one-line description of what it does
- These will be specced in detail during the build phase
## What NOT to Do
- Do not wrap native components in custom abstractions
- Do not use UIKit unless SwiftUI has no equivalent
- Do not create custom navigation transitions unless specified
- Do not add animations beyond SwiftUI defaults unless specified
- Do not hardcode strings
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.
- 1mo ago First seen · 137 lines · 66 tokens per session scan A caa4fa202f59
app-spec is a skill published in the GitHub repository troyjthomas/ios-agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 1,169 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
docker-environments
Docker-aware Mémoire operation — CI/CD headless pipelines, shared MCP server, agent worker containers, and Figma bridge port-forwarding for containerized setups.
motion-video
Product animation, UI motion, portfolio videos — Apple-grade reveals, motion tokens, full production pipelines.
usability-testing
Usability testing frameworks — test planning, task scenarios, moderated and unmoderated protocols, analysis frameworks, and insight synthesis for Mémoire research pipeline.
vue-gen
Vue 3 Composition API code generation — transforms Mémoire component specs into Vue SFCs with script setup, Tailwind styling, and composable patterns.
figma-generate-design
Create new Figma screens and pages using existing components, variables, and design system.
figma-generate-library
Generate Figma component library from React/shadcn codebase with Code Connect parity.