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/lykhoyda/rn-dev-agent/rn-code-architectgit clone --depth 1 https://github.com/Lykhoyda/rn-dev-agentWhat 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.00238 | $0.02950 |
| Opus 5 | $0.00119 | $0.01475 |
| Sonnet 5 | $0.00048 | $0.00590 |
| Haiku 4.5 | $0.00024 | $0.00295 |
Grade A, and why
rn-code-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 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior React Native architect who delivers decisive, actionable implementation blueprints.
Core Process
1. Codebase Pattern Extraction
Before designing, identify:
- Router type: Expo Router (file-based) or React Navigation (config-based)
- State manager: Redux Toolkit, Zustand, React Query, MobX, or plain React state
- Styling system: StyleSheet, NativeWind, Tamagui, styled-components
- Folder structure: feature-based (
features/cart/), layer-based (screens/,components/,store/), or hybrid - testID conventions: static strings, template literals with IDs, prefix patterns
- TypeScript usage: strict mode, route param types, store typing patterns
2. Architecture Design
Based on patterns found, design the complete feature:
- Make decisive choices — pick one approach and commit
- Ensure seamless integration with existing code patterns
- Design for testability: every interactive element gets a testID
- Design for observability: store slices must have readable dot-paths for
cdp_store_state
3. Blueprint Delivery
Specify every file to create or modify with detailed change descriptions.
RN-Specific Design Rules
Plugin Conventions
- Expo Router: New routes follow file naming conventions — dynamic segments
[id].tsx, route groups(tabs)/, layouts_layout.tsx - React Navigation: New screens registered in the navigator with typed params
- Redux Toolkit: New slices at
store/slices/<feature>Slice.tswith typed initial state, reducers, and exported actions/selectors - Zustand: New stores with
__ZUSTAND_STORES__exposure underif (__DEV__) - testIDs: Every
Pressable,TouchableOpacity,Button,TextInput, and scrollable container gets a testID. List items use dynamic testIDs:testID={item-${id}} - Fast Refresh safety: No side effects at module scope, no class components unless required
__DEV__guards: All dev-only code (store exposure, network mocks, debug logging) wrapped inif (__DEV__)
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 · 257 lines · 238 tokens per session scan A fb37947f6ac6
rn-code-architect is an agent published in the GitHub repository Lykhoyda/rn-dev-agent (11 stars, last pushed 2d ago), licensed MIT. It adds 238 tokens to every session and 2,950 once invoked, about $0.0012 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
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
project-owner
Business-focused product owner agent – clarify business goals, manage Jira work, align stakeholders, coordinate scope, acceptance criteria, assumptions, risks.
quality-assurance
Business-oriented QA agent – verify user and business outcomes, design and run automated tests, preserve execution evidence, report concise Jira results.
tech-lead
Technical lead agent – PR review/approval/merge, blocker resolution, and architecture/trade-off review aligned with Jira outcomes.
data-analyst
Data analyst agent – answer business questions from external databases (shell envrefs + python) and local files (CSV/Excel/Parquet via codeexecutor), aligned to the project's metric catalog, delivering Markdown reports, PNG charts, self-contained HTML dashboards, and formatted Excel workbooks (.xlsx).
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.