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 agents/terryc21/workflow-audit/layer5-data-wiringgit clone --depth 1 https://github.com/Terryc21/workflow-auditWhat 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.00000 | $0.02553 |
| Opus 5 | $0.00000 | $0.01277 |
| Sonnet 5 | $0.00000 | $0.00511 |
| Haiku 4.5 | $0.00000 | $0.00255 |
Grade A, and why
layer5-data-wiring 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 2d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layer 5: Data Wiring Audit
Note: Grep commands and concrete examples in this file are drawn from a real workflow-audit run on the Stuffolio codebase (paths like
Sources/Features/RepairKeepReplace/, manager names likePriceWatch). The detection patterns are reusable methodology; specific managers and features are project-specific. Substitute your project's equivalents. A full sample scan lives inexamples/sample-stuffolio-scan/.
Purpose
Layer 5 verifies that features use real user data instead of mock/hardcoded values, and that model capabilities are fully wired into the features that need them. While Layers 1-4 audit navigation and UX, Layer 5 audits whether the data flowing through those workflows is genuine.
Why This Layer Exists
A feature can pass all navigation audits (correct entry point, proper sheet handling, good feedback) and still be useless if it shows fabricated data. The Repair/Keep/Replace feature was the canonical example: well-architected UI, correct navigation, but the decision engine used a 4-rule if/else chain ignoring repair costs, warranty data, and Price Watch prices that the app already tracked.
The symptom: Feature looks functional. User makes decisions based on it. Data is fake.
What Layer 5 Catches
| Issue Type | Example | Severity |
|---|---|---|
| Mock Data | asyncAfter delay + hardcoded values simulating a fetch |
🔴 Critical |
| Unwired Data | Item has rmaRecords with repair costs, but decision engine ignores them |
🟠 High |
| Placeholder AI | "Find Alternatives" button that returns static array | 🔴 Critical |
| Simplified Logic | 4-rule if/else when 10+ data points are available | 🟠 High |
| Platform Parity | Extension file can't resolve properties on macOS | 🟠 High |
| Unused Integration | Price Watch tracks prices, but no feature reads them | 🟠 High |
Detection Process
Step 1: Model Inventory
Catalog what data the app actually tracks:
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.
- 2d ago First seen · 247 lines · 0 tokens per session scan A e3a2f48b7da6
layer5-data-wiring is an agent published in the GitHub repository Terryc21/workflow-audit (58 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,553 tokens. 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 agents, from other repositories
Native SwiftUI Builder
Builds complex custom SwiftUI views using standard SwiftUI components with TTBaseUIKit design tokens (XView/XSize/XFont). Does NOT use TTBaseSUI wrapper components.
Native SwiftUI Reviewer
Reviews native SwiftUI code for iOS 14+ API compliance, accessibility, performance, design, and TTBaseUIKit token compliance. Does NOT check for TTBaseSUI components.
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.
Accessibility Audit
Audits iOS accessibility: VoiceOver labels/hints/traits, Dynamic Type, touch targets, color contrast, element grouping.
Refactor SwiftUI View
Refactors SwiftUI views: extracts subviews, enforces TTBaseSUI patterns, stabilizes view tree, organizes code structure.
Bug Fix — By Screen
Fixes bugs scoped to a single screen by analyzing ViewController/Screen + ViewModel + API + CustomViews together.