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/nicelight/devrails-26/add-testsgit clone --depth 1 https://github.com/nicelight/DevRails-26What 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.00014 | $0.00784 |
| Opus 5 | $0.00007 | $0.00392 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
add-tests 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 3d 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
/add-tests - Improve task-scoped coverage
<input_contract>
Require one explicit TASK-NNN-TN-FT-NNN-WN that:
- resolves uniquely through
.memory-bank/tasks/index.json; - has
status: in_progress; - has an outcome/AC/REQ/spec boundary covering the proposed test behavior.
Read the task record, .memory-bank/workflows/tier-policy.md#tier-obligations,
#closure-authority, #hard-write-boundary when applicable, linked
specs/verification targets, implementation evidence, and project-native test
configuration needed for the chosen check.
</input_contract>
<hard_invariants>
- Reuse the existing task ID, lifecycle, tier, protocol, and evidence paths. Do not create synthetic testing tasks, a second lifecycle, or new task fields.
- Test files outside advisory
touched_filesare allowed only for the same outcome and inside hard allowed/forbidden scopes; record the deviation. - Do not weaken assertions, disable failures, introduce decorative tests, or substitute screenshots for behavior proof.
- Do not create or modify
.memory-bank/testing/; accepted shared testing-spec changes route through/spec-redesign, Foundation detail through/foundation-to-tasks, and feature detail through/feature-to-tasks. /add-testsdoes not own task closure or scheduler transitions. </hard_invariants>
<operator_decisions> If useful coverage requires a new product behavior, contract, state/data, security/compatibility rule, task-boundary/tier change, external dependency, or verification-policy choice not already settled, stop and surface the exact decision.
Interactive flow asks the operator and resumes only after the owning
feature/spec/task plan is durably repaired. Unattended flow returns the blocker
to the scheduler without choosing and names /feature-to-tasks FT-<NNN>,
/spec-redesign, or /feature-doctor FT-<NNN> as the applicable resume route.
A recommendation is not an accepted decision.
</operator_decisions>
<agent_discretion> The agent chooses exploration order, tools, test level, test shape, fixtures, and proportional flakiness checks. Select the narrowest credible proof: a unit, integration/contract, e2e, or existing project-native check according to the actual behavior and regression risk. No requirement exists to fill every test category or put browser/e2e first. </agent_discretion>
<required_outputs>
- scoped test changes;
- exact commands/results and substantive artifacts in the existing task's
tier-selected paths:
- T0/T1 ->
.protocols/<TASK_ID>/run.md; - T2/T3 -> full protocol state plus
.tasks/<TASK_ID>/evidence;
- T0/T1 ->
- recorded actual test files, advisory deviations, hard-scope compliance, flakiness evidence when relevant, and remaining blockers. </required_outputs>
<handoff_contract>
Return immediately to /exe, /verify, the scheduler, or the explicit task
owner under .memory-bank/workflows/tier-policy.md#closure-authority.
Out-of-scope coverage routes to normal /feature-to-tasks FT-<NNN> planning
instead of being smuggled into the current task.
</handoff_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.
- 3d ago First seen · 81 lines · 14 tokens per session scan A 8c7bb8c95773
add-tests is a command published in the GitHub repository nicelight/DevRails-26 (22 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 784 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
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.