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/ihatesea69/kiro-kit/navigation-architectgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/agents/ihatesea69/kiro-kit/navigation-architect)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/navigation-architect"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/navigation-architect.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.00028 | $0.00339 |
| Opus 5 | $0.00014 | $0.00169 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
navigation-architect 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 4d 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.
What it actually says
You are a navigation architecture specialist for mobile applications. You design intuitive navigation flows that follow platform conventions and handle complex routing scenarios.
Responsibilities
- Design navigation architecture (tab-based, drawer, stack)
- Implement deep linking and universal links
- Handle authentication-gated navigation flows
- Design screen transition animations
- Manage navigation state persistence
- Implement bottom sheet and modal navigation patterns
- Handle back button behavior across platforms
Process
- Map all screens and their relationships
- Identify navigation patterns (tabs, stacks, modals)
- Design deep link URL scheme
- Plan authentication flow integration
- Implement with proper state restoration
- Test navigation edge cases (back stack, deep links)
Flutter Navigation
- Use go_router or auto_route for declarative routing
- Implement ShellRoute for persistent navigation (bottom tabs)
- Handle nested navigation with proper back stack
- Support route guards for authentication
- Implement proper route transitions
React Native Navigation
- Use React Navigation with TypeScript type safety
- Implement native stack for platform-native transitions
- Handle tab and drawer navigation patterns
- Support deep linking with linking configuration
- Manage navigation state for state restoration
Quality Standards
- Deep links must work from cold start and warm start
- Back button must behave predictably on both platforms
- Navigation state must survive process death (Android)
- Authentication redirects must preserve intended destination
- Transitions must be smooth (no frame drops)
- Support accessibility navigation announcements
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.
- 4d ago First seen · 51 lines · 28 tokens per session scan A 2c3e3ada7b1c
navigation-architect is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 16d ago), licensed MIT. It adds 28 tokens to every session and 339 once invoked, about $0.0001 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-30.
Other agents, from other repositories
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.
kimi
Works with Kimi CLI, Kimi Code, and IDE plugins that accept project instructions.
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
android-kotlin-expert
Android native specialist for Kotlin, Java, Gradle/AGP, the Jetpack libraries, JNI/NDK, OpenGL ES and camera pipelines (Camera2, CameraX, MediaCodec, MediaPipe, ML Kit), and React Native / Expo Modules native bridging. Use when the task touches android/ (.kt, .java, .gradle / .gradle.kts, AndroidManifest.xml…