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/mrvladd-d/memobank/add-testsgit clone --depth 1 https://github.com/mrvladd-d/memobankWrote 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/mrvladd-d/memobank/add-tests)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/add-tests"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/add-tests.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 | $0.00021 | $0.00260 |
| Opus 5 | $0.00010 | $0.00130 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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 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
/add-tests — Improve test coverage
- Определи типы тестов:
- unit: чистая логика
- integration: границы (DB/API)
- e2e: критические user flows
Если есть UI:
- browser e2e через Playwright / agent-browser / CDP
- обязательно сохраняй screenshots/videos/traces как evidence
- Выбери приоритет:
- сначала e2e на core value
- потом unit на критические инварианты
- для сервисов/API добавь integration/contract tests раньше “декоративных” UI-тестов
- Реализуй
- добавь тесты
- убедись, что они не flaky
- Обнови
.memory-bank/testing/index.md
- какие тесты добавлены
- как их запускать
- Артефакты (логи/скриншоты) →
.tasks/TASK-TESTS-.../
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 · 37 lines · 21 tokens per session scan A af40246537ce
add-tests is a command published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 260 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
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
testing
Comprehensive testing through distributed execution.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
test
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.
test
Escrever e rodar testes (skill 05 — QA Engineer).