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 skills/radimsem/remindb/add-integration-testnpx skills add radimsem/remindb --skill add-integration-testgit clone --depth 1 https://github.com/radimsem/remindbWrote 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/skills/radimsem/remindb/add-integration-test)<a href="https://agentmods.dev/skills/radimsem/remindb/add-integration-test"><img src="https://agentmods.dev/badge/skills/radimsem/remindb/add-integration-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 | $0.00093 | $0.01852 |
| Opus 5 | $0.00046 | $0.00926 |
| Sonnet 5 | $0.00019 | $0.00370 |
| Haiku 4.5 | $0.00009 | $0.00185 |
Grade A, and why
add-integration-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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add an integration test
Integration tests live at the repo root in package remindb_test, not inside a pkg/. They exercise the full pipeline — a real store, real compiler, real MCP transport — against fixtures under testdata/. There are two flavors:
| Flavor | File | Use when |
|---|---|---|
| Direct API | integration_test.go |
Testing compiler / query / store / transformer end-to-end without MCP |
| MCP | mcp_integration_test.go |
Testing the user-visible tool surface as an agent would call it |
Pick the flavor by the question you're asking. "Does the compiler emit the right shape from this fixture?" → direct. "Does an agent calling MemorySearch after MemoryCompile see the expected ranking?" → MCP.
Where it lands
| File | What changes |
|---|---|
integration_test.go or mcp_integration_test.go |
Add a Test<Scenario> function |
testdata/<scenario-name>/ |
New fixture directory (only if existing fixtures don't match) |
Fixture directories are flat namespaces (testdata/openclaw/, testdata/<your-scenario>/). One fixture set per scenario family; reuse aggressively.
The two helpers
Both files lean on package helpers — never reach for raw store.Open or raw mcp.NewServer in a test.
internal/testutil.OpenTestDB(t)— opens an in-memory:memory:SQLite store with migrations applied; auto-cleans ont.Cleanup. Use for direct-API tests.internal/mcptest.NewEnv(t)— opens the test DB, wires a default-config server + tracker, connects an in-memory MCP transport, and exposesenv.CallTool(t, name, args)andenv.TextContent(t, result). Use for MCP tests.
Direct-API template
Mirror integration_test.go:TestOpenClawAgentWorkflow. Walk a real workflow stage by stage, log progress, assert at each stage:
package remindb_test
import (
"context"
"strings"
"testing"
"github.com/radimsem/remindb/internal/testutil"
"github.com/radimsem/remindb/pkg/compiler"
"github.com/radimsem/remindb/pkg/query"
)
func TestNewScenario(t *testing.T) {
st := testutil.OpenTestDB(t)
ctx := context.Background()
// Stage 1: compile fixtures.
result, err := compiler.CompileDir(ctx, st, "testdata/<scenario>", "<source-id>")
if err != nil {
t.Fatalf("CompileDir: %v", err)
}
if result.Added == 0 {
t.Fatal("expected nodes from fixtures")
}
t.Logf("compiled: +%d ~%d -%d (%d total)", result.Added, result.Modified, result.Removed, result.Total)
// Stage 2: query.
engine := query.NewEngine(st)
res, err := engine.Search(ctx, "<query>", 1000)
if err != nil {
t.Fatalf("Search: %v", err)
}
if len(res.Nodes) == 0 {
t.Fatal("expected search hits")
}
}
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 · 149 lines · 93 tokens per session scan A 15df2a9a3433
add-integration-test is a skill published in the GitHub repository radimsem/remindb (125 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 1,852 once invoked, about $0.0005 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 skills, from other repositories
uat-testing
Run end-to-end User Acceptance Tests for Agent Brain features. Builds wheels, installs packages, starts a test server, runs tests, and reports results — all without permission prompts.
e2e-pom
Build and maintain Page Object Models by live element discovery — never by guessing selectors. Build mode pairs with the user: derives the element inventory from test cases, proves every locator against the running app, and confirms with highlighted screenshots before anything enters the POM. Heal mode runs…
e2e-setup
Set up Playwright e2e automation tailored to this team and app. Probes the running app (auth mechanism, API surface, spec availability), interviews with recommendations instead of open questions, scaffolds the playwright/ folder, and records every decision in playwright/AUTOMATION.md for the other e2e skills to read.…
test-cases
Generate test cases from a Jira ticket's acceptance criteria. Produces e2e test scenarios (steps and expected results, no code) and a unit test checklist for developers. Test cases map back to requirements for traceability. Use when: "write test cases", "generate tests", "e2e tests for PROJ-789", "test cases for this…
verify-fix
Re-test a bug fix after a developer resolves it. Pulls the original bug from Jira, re-executes the repro steps in the browser, checks for regressions, and updates the bug status. The final step in the SDT workflow before a ticket moves to Done. Use when: "verify fix", "retest", "is this fixed?", "check BUG-123"…
human-pass
Guide real-build acceptance: literal taps, real inputs, expected outcomes, worst case first, one sitting. Triggers: testflight, human pass, acceptance test, before we ship, hand it to the user, what should I test, release checklist, device test.