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/digi-uw/openelis-global-2/write-backend-testgit clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/digi-uw/openelis-global-2/write-backend-test)<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/write-backend-test"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/write-backend-test.svg" alt="Measured on agentmods" 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.00000 | $0.00238 |
| Opus 5 | $0.00000 | $0.00119 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
write-backend-test 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 5d 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
Command: /write-backend-test
Description
Generates a new service-layer integration test following the OpenELIS Global 2 standards.
User Input
$ARGUMENTS
Parameters
service: The service to test (for example,PatientService).module: The module package name (e.g.,patient).
Implementation Logic
- Locate the target class to understand its dependencies and methods.
- Identify dependencies that need to be mocked (external) vs. autowired (internal).
- Generate the test class using
.ai/skills/backend-integration-testing/templates/integration-test-template.java.template. Replace every placeholder and the failing sentinel with working code. - Create or reuse a DBUnit XML dataset under
src/test/resources/testdata/and load it in@Before. - Run the specific test with
mvn test -Dtest=<GeneratedIntegrationTest>and report the result.
Example Usage
/write-backend-test service=PatientService module=patient
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.
- 5d ago First seen · 35 lines · 0 tokens per session scan A 822fe24e6a46
write-backend-test is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (251 stars, last pushed today), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 238 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-30.
Other commands, from other repositories
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.