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/lykhoyda/rn-dev-agent/lock-e2egit 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.00060 | $0.00296 |
| Opus 5 | $0.00030 | $0.00148 |
| Sonnet 5 | $0.00012 | $0.00059 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
lock-e2e 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
Lock the action into a locked e2e test: $ARGUMENTS
Steps:
- Call
cdp_lock_e2e_testwithactionId= the first positional arg (addrelock: trueif--relockis present). - If it returns
STRICT_RUN_FAILED, tell the user the action must pass a strict (no-repair) run first — offer to runcdp_run_actionto repair it, then retry the lock. - If it returns
PARAMS_UNSUPPORTED, explain that v1 supports param-free tests only. - On success, report the frozen file path and that it will now be included in
cdp_run_e2e_suite. - For login, this locked test is the formal PR proof on the exact candidate.
cdp_login_prologueis only a navigation helper and must not be treated as that proof.
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 · 16 lines · 60 tokens per session scan A e1b6ccd3c433
lock-e2e is a command published in the GitHub repository Lykhoyda/rn-dev-agent (11 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 296 once invoked, about $0.0003 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 commands, from other repositories
dashboard-flow-auto
Toggle autonomous mode for a session's flow. Usage /dashboard:flow-auto.
dashboard-flow-abort
Abort the running flow on a session. Usage /dashboard:flow-abort.
dashboard-git-branches
List git branches for the current dir (current marked ). Runs locally, no LLM.
brainstorm
Command dispatcher for brainstorm.
discover
Command dispatcher for discover.
propose
Command dispatcher for propose.