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/layer3-issue-detectiongit 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.12289 |
| Opus 5 | $0.00000 | $0.06144 |
| Sonnet 5 | $0.00000 | $0.02458 |
| Haiku 4.5 | $0.00000 | $0.01229 |
Grade A, and why
layer3-issue-detection 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 — 1,426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layer 3: Issue Detection
Note: Specific examples in this file ("Real examples caught in Stuffolio v1.0," concrete file paths like
Sources/Features/...) are drawn from a real workflow-audit run on the Stuffolio codebase. They are illustrative — the issue categories are the reusable methodology; the paths and findings are project-specific. A full sample scan lives inexamples/sample-stuffolio-scan/.
Purpose
Layer 3 systematically scans ALL entry points from Layer 1 and applies issue detection rules. Unlike Layer 2 (which traces specific flows in depth), Layer 3 does a breadth-first scan to categorize issues across the entire codebase.
Issue Categories
Category 1: Dead Ends
Entry point leads nowhere or to wrong destination.
Detection patterns:
// Navigation to section that doesn't contain the feature
selectedSection = .tools // but feature not in ToolsView
// Sheet case exists but handler missing
case .featureName // in enum but no case in sheetContent(for:)
// View exists but no entry point
struct OrphanedFeatureView // never presented
Severity: 🔴 CRITICAL
Category 2: Incomplete Navigation
User lands on section but must find feature manually.
Detection patterns:
// Section navigation without deep link
selectedSection = .tools // lands at top, feature buried
// No scroll target or anchor
// No programmatic focus
Severity: 🟠 HIGH
Category 3: Missing Auto-Activation
Feature requires mode/state that isn't set.
Detection patterns:
// Navigation without state setup
selectedSection = .myProducts // but isSelectMode not set
// Sheet without pre-population
activeSheet = .edit // but selectedItem not set
Severity: 🟠 HIGH
Category 4: Promise-Scope Mismatch
A specific-sounding CTA opens a generic/overly-broad destination. The user is promised a focused action but gets a container with the action buried among unrelated content.
Different from "Wrong Destination" (user is in the right place, just too much of it) and "Incomplete Navigation" (about scroll position, not destination scope).
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 · 1,426 lines · 0 tokens per session scan A 7a08dbe0ac3c
layer3-issue-detection 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 12,289 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.