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/nicelight/DevRails-26Wrote 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/nicelight/devrails-26/start)<a href="https://agentmods.dev/commands/nicelight/devrails-26/start"><img src="https://agentmods.dev/badge/commands/nicelight/devrails-26/start/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/nicelight/devrails-26/start"><img src="https://agentmods.dev/badge/commands/nicelight/devrails-26/start.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.00032 | $0.00582 |
| Opus 5.5 | $0.00013 | $0.00233 |
| Sonnet 5.5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
start 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.
What it actually says
/start — Resolve next workflow owner
<input_contract>
Use $ARGUMENTS as operator focus when present.
If .memory-bank/ is missing, treat the repository root as <target-repo>
unless the operator supplied another target. Accept <devrails-checkout> only
when supplied by the operator or already verifiable by its
scripts/install-framework.mjs.
When both paths are known, return this command with shell-safe resolved paths:
node <devrails-checkout>/scripts/install-framework.mjs --bootstrap --target <target-repo> --yes
Otherwise ask for the checkout path and stop. Do not call /mb-init, run local
bootstrap logic, copy helpers, install dependencies, or create the skeleton.
After external bootstrap, rerun /start.
When .memory-bank/ exists, read .memory-bank/index.md,
.memory-bank/workflows/execute-loop.md#interactive-mode-you-stay, and only
the product, PRD, baseline, spec/foundation, feature, task, review, protocol, or
handoff records needed to resolve the current incomplete boundary. File
existence and conversation memory are not workflow state; use authoritative
statuses, verdicts, Planning Revision, dependencies, and durable handoffs.
</input_contract>
<hard_invariants>
/startwrites no artifact or lifecycle state; the selected skill owns its mutations and handoff.- Select no unattended mode without an explicit operator instruction.
- Do not create roadmap or task state without a clarified PRD/delta.
- Do not bypass an existing review, Foundation, dependency, doctor, tier, or operator-decision gate.
- Do not choose among multiple eligible features or tasks without an authoritative target. </hard_invariants>
<routing_contract>
Prefer a valid unfinished durable handoff or resume route. Otherwise select the
first incomplete boundary in the interactive execute-loop whose prerequisites
are satisfied. Substantial existing code without a current evidence-backed
baseline routes to /map-codebase before new product planning.
Invoke the one selected owning skill and stop routing. If the owner or target depends on an unresolved operator choice, ask that one question and stop. Do not output or execute a downstream chain. </routing_contract>
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 · 66 lines · 32 tokens per session scan A 48dbce500526
start is a command published in the GitHub repository nicelight/DevRails-26 (23 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 582 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
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.