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.
git clone --depth 1 https://github.com/Lykhoyda/rn-dev-agentWrote 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/lykhoyda/rn-dev-agent/end-session)<a href="https://agentmods.dev/commands/lykhoyda/rn-dev-agent/end-session"><img src="https://agentmods.dev/badge/commands/lykhoyda/rn-dev-agent/end-session/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/lykhoyda/rn-dev-agent/end-session"><img src="https://agentmods.dev/badge/commands/lykhoyda/rn-dev-agent/end-session.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00030 | $0.01442 |
| Opus 5.5 | $0.00012 | $0.00577 |
| Sonnet 5.5 | $0.00006 | $0.00288 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
end-session 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 1mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/end-session — session wrap-up
A maintainer ritual for this repository. It reconstructs the session, classifies durable knowledge by owner, and returns reviewable handoffs without writing to another repository.
| Owner | Canonical destination | Content |
|---|---|---|
| rn-dev-agent-workspace | Engineering docs | Process, planning, routine engineering decisions, bugs, stories, specifications, diagnostics, comparisons, and research |
| Anton Factory | architect-docs | Captain-approved architecture vision, ADRs, authority contracts, settled decisions, evidence indexes, and architecture changelogs |
| rn-dev-agent | apps/docs-site |
Public product and user documentation only |
$ARGUMENTS is an explicit maintainer focus. Weave it into the reconstruction; it does
not replace evidence gathering.
Iron rules
- Read other repositories; never write them. Produce exact handoff blocks and target links in the final report. Do not edit a sibling checkout, clone another repository, or add cross-repository automation.
- Never create top-level
docs/here. Engineering material belongs in the workspace; product documentation remains underapps/docs-site. - Classify before drafting. Routine engineering and process decisions go to workspace docs. Only captain-approved, settled architecture goes to Anton Factory architect-docs. An unapproved proposal remains workspace planning material, never a Factory ADR.
- Use pointers across owners. A Factory architecture handoff links to workspace process evidence instead of copying its narrative. A workspace handoff links to any accepted Factory record instead of duplicating the architecture record.
- Never fabricate. Omit a handoff category when the session produced nothing that
qualifies. Use today's date from
date +%Fand preserve the destination's established format and sequence when it can be read. - GitHub mutation is gated. Creating issues and applying Kano labels are the only outward writes. Present the exact plan and wait for explicit maintainer confirmation.
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.
- 1mo ago First seen · 136 lines · 30 tokens per session scan A ad95b8682729
end-session is a command published in the GitHub repository Lykhoyda/rn-dev-agent (20 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,442 once invoked, about $0.0001 per session on Opus 5.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-session-abort-all
Abort multiple running sessions (asks which). Usage /dashboard:session-abort-all.
dashboard-session-abort
Abort the current run of a session. Usage /dashboard:session-abort.
dashboard-session-kill
Shut down (kill) a session. DESTRUCTIVE. Usage /dashboard:session-kill.
dashboard-session-rename
Rename a session. Usage /dashboard:session-rename.
dashboard-session-spawn
Spawn a new session in a directory. Usage /dashboard:session-spawn [cwd].
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.