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 commands/senaiverse/reactnative-expo-ai-agent-system-workflow/featuregit clone --depth 1 https://github.com/senaiverse/reactnative-expo-ai-agent-system-workflowWrote 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/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/feature)<a href="https://agentmods.dev/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/feature"><img src="https://agentmods.dev/badge/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/feature.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.00012 | $0.00555 |
| Opus 5 | $0.00006 | $0.00278 |
| Sonnet 5 | $0.00002 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade C, and why
feature scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- 🌟 SenaiVerse - Claude Code Agent System v1.0 --> How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Implementation Workflow
Implements: $ARGUMENTS
Execution Plan
Execute the following multi-agent workflow:
Phase 1: Planning & Analysis
-
Grand Architect Analysis
- Invoke @grand-architect to break down the feature
- Analyze architectural impact
- Identify affected files and components
- Assess complexity and risks
-
Feature Impact Assessment
- Estimate implementation time
- Identify dependencies
- Determine if breaking changes are involved
Phase 2: Security & Architecture Review
-
Security Audit (if feature involves):
- User data, authentication, payments, or sensitive operations
- Invoke @security-specialist for OWASP Mobile Top 10 check
-
State Management Planning
- Determine state architecture needed
- Plan Redux/Context integration
- Design data flow
Phase 3: Implementation
-
Create Feature Structure
- Generate necessary files (components, hooks, services)
- Follow project conventions from CLAUDE.md
-
Write Core Logic
- Implement business logic
- Add proper TypeScript types
- Follow design system tokens
-
Cross-Platform Validation
- Ensure iOS and Android compatibility
- Handle platform-specific cases if needed
Phase 4: Quality Assurance
-
Generate Tests (@test-generator)
- Unit tests for business logic
- Component tests for UI
- E2E tests if critical flow
-
Accessibility Check (@a11y-enforcer)
- Validate all interactive elements
- Check color contrast
- Verify touch targets
-
Performance Check (@performance-prophet)
- Predict performance impact
- Check for potential bottlenecks
- Validate bundle size increase
Phase 5: Final Review
-
Code Review (/@review)
- Run comprehensive review
- Fix any issues found
-
Documentation
- Add inline comments for complex logic
- Update CLAUDE.md if needed
Success Criteria
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.
- 5d ago First seen · 101 lines · 12 tokens per session scan C 47d78bdff92c
feature is a command published in the GitHub repository senaiverse/reactnative-expo-ai-agent-system-workflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 555 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
brooks-audit
Run a Brooks-Lint architecture audit.
focus-report
One-screen focus snapshot — avg turn duration, thinking-block usage, and longest sessions.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.