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/callstack/react-native-testing-library/example-appsgit clone --depth 1 https://github.com/callstack/react-native-testing-libraryWhat 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.00629 |
| Opus 5 | $0.00000 | $0.00315 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
example-apps 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 yesterday.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example App Regeneration
General workflow
- Regenerate Expo example apps in a temporary directory, then copy the fresh scaffold into place.
- Before replacing an example app, move the current app directory to
/tmpso repo-specific files can be restored selectively. - Avoid image churn: preserve existing tracked image assets unless the task explicitly asks to update them or the new SDK requires an asset change.
- After copying a generated app into
examples/, remove the generated.gitdirectory andnode_modules, then reinstall from inside the repo workspace.
examples/basic
- Generate from the Expo blank TypeScript template:
yarn create expo-app /tmp/rntl-basic-fresh --template blank-typescript --yes
- Restore these repo-specific files on top of the fresh scaffold:
App.tsxcomponents/__tests__/theme.tsjest.config.jsjest-setup.tsbabel.config.jseslint.config.mjsREADME.mdAGENTS.md- existing tracked image assets in
assets/ .expo-shared/assets.jsonif it existed before
- Keep the fresh Expo entrypoint
index.ts. - Update
package.jsonandapp.jsonto match repo naming and scripts. Keepapp.jsonpointing at the restored existing image assets unless changing them is intentional.
examples/cookbook
- Generate from a router-enabled Expo scaffold:
yarn create expo-app /tmp/rntl-cookbook-fresh --example with-router --yes
- Restore these repo-specific files on top of the fresh scaffold:
app/- tutorial test directories such as
basics-tutorial/andbasics-tutorial-react-strict-dom/ theme.tsjest.config.jsjest-setup.tsbabel.config.js.eslintrc.eslintignoreREADME.mdAGENTS.md- custom assets not present in the scaffold, such as
assets/gradientRNBanner.png - existing tracked image assets in
assets/ .expo-shared/assets.jsonif it existed before
- Keep the fresh Expo Router entry setup.
- Reapply the cookbook-specific dependency set in
package.jsonandapp.json. Keepapp.jsonpointing at the restored existing image assets unless changing them is intentional.
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.
- yesterday First seen · 62 lines · 0 tokens per session scan A f4046624bd25
example-apps is an agent published in the GitHub repository callstack/react-native-testing-library (3,414 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 629 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
business-analyst
Business Analyst. Domain understanding, ubiquitous language, business rules, and bounded contexts; bridge collaboration, not message ferrying. Triggers: domain analysis, business rules, ubiquitous language, bounded context, Analysis Patterns, Business Analysis.
customer
End user (Customer). Product feedback and improvement suggestions from a user perspective. Triggers: user feedback, customer perspective, experience critique, improvement ideas, usability. Use proactively when reviewing UI flows or after feature demos.
developer
Follow existing project style with minimal implementation.
orchestrator
Minimal orchestrator. Read Jira issues and invoke sub-agents as needed.
ux-designer
UX designer. Interaction design, user experience optimization, and usability improvements. Triggers: UX design, interaction optimization, user experience.
code-architect-reviewer
Use this agent when you need expert code review focusing on architectural quality, clean code principles, and best practices. Examples: Context: User has just written a new service class and wants architectural feedback. user: 'I just implemented a user authentication service. Can you review it?' assistant: 'I'll use…