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 skills/moasq/ios-dev-agent/feature-directory-structurenpx skills add moasq/ios-dev-agent --skill feature-directory-structuregit clone --depth 1 https://github.com/moasq/ios-dev-agentWrote 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/moasq/ios-dev-agent/feature-directory-structure)<a href="https://agentmods.dev/skills/moasq/ios-dev-agent/feature-directory-structure"><img src="https://agentmods.dev/badge/skills/moasq/ios-dev-agent/feature-directory-structure.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.00066 | $0.01170 |
| Opus 5 | $0.00033 | $0.00585 |
| Sonnet 5 | $0.00013 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
feature-directory-structure 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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Directory Structure
Features with many files must use nested subdirectories. Flat is fine up to a point; past that, subfolders are required.
The Rule
Flat — up to 5 files total per feature
When a feature has 5 or fewer files, keep it flat:
Features/Profile/
ProfileView.swift
ProfileViewModel.swift
ProfileView+Header.swift
Three files, still scannable. No need for subfolders.
Nested — 6+ files per feature
Past ~5 files, group into subfolders by role:
Features/Home/
HomeView.swift ← main shell (body is table of contents)
HomeViewModel.swift ← one @Observable class
Sections/ ← extracted body sections (View+X.swift)
HomeView+Idle.swift
HomeView+Recording.swift
HomeView+Result.swift
Sheets/ ← .sheet / .fullScreenCover contents
PillarDetailSheet.swift
HistoryBrowseSheet.swift
Overlays/ ← ZStack overlays, toasts, celebration
CelebrationOverlay.swift
StreakToastView.swift
Backdrop/ ← ambient backgrounds, visual effects
AmbientBackdrop.swift
The shell (HomeView.swift + HomeViewModel.swift) stays at the feature root. Everything else goes into a subfolder.
Canonical Subfolder Names
Use these names consistently across features. Don't invent new ones.
| Folder | What goes in it |
|---|---|
Sections/ |
View+X.swift extensions — extracted body sections of the main view |
Sheets/ |
Views presented via .sheet or .fullScreenCover — each is its own standalone View |
Overlays/ |
ZStack overlays, toasts, celebration cards, modal affordances |
Backdrop/ |
Ambient backgrounds, particle scenes, blur effects, visual-only layers |
Components/ |
Feature-local reusable subviews that don't fit the above and aren't shared (shared components belong in Features/Common/) |
Rows/ |
List row views when a feature has 3+ row variants |
When NOT to split
Don't create a subfolder for a single file. Sheets/PillarDetailSheet.swift alone is fine only if you expect another sheet to land in v1.1 — otherwise keep it at the feature root until a second sheet forces the split.
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.
- 3d ago First seen · 117 lines · 66 tokens per session scan A 90d3a773e345
feature-directory-structure is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 1,170 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…