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/ohah/react-native-mcp/setup-mcpgit clone --depth 1 https://github.com/ohah/react-native-mcpWhat 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.00256 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
setup-mcp 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.
What it actually says
MCP 명령을 사용자 환경에 맞게 설정
MCP 서버는 mise 경로를 command로 씁니다. Cursor는 PATH를 거의 비운 채로 MCP를 실행해서, 각 사용자가 자신의 mise 경로로 .cursor/mcp.json을 한 번 갱신해야 합니다.
할 일
저장소 루트에서 아래 명령을 실행하세요:
bun run setup-mcp
또는:
bun run .cursor/scripts/set-mcp-mise-path.ts
mise가 PATH에 있으면 그 경로를 찾아.cursor/mcp.json의 MCP 서버command를 해당 경로로 덮어씁니다.mise가 PATH에 없으면~/.local/bin/mise,/opt/homebrew/bin/mise등 흔한 설치 위치를 찾아 씁니다.- 실행 후 Cursor를 한 번 재시작하면 MCP가 새 경로로 동작합니다.
/setup-mcp 실행 시
에이전트가 위 bun run setup-mcp를 실행해 사용자 환경에 맞게 .cursor/mcp.json을 갱신합니다.
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 · 26 lines · 0 tokens per session scan A 65191199718d
setup-mcp is a command published in the GitHub repository ohah/react-native-mcp (7 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 256 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.