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/packmindhub/packmind/cli-e2e-test-authoringnpx skills add PackmindHub/packmind --skill cli-e2e-test-authoringgit clone --depth 1 https://github.com/PackmindHub/packmindWhat 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.00056 | $0.01487 |
| Opus 5 | $0.00028 | $0.00744 |
| Sonnet 5 | $0.00011 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
cli-e2e-test-authoring 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 2d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI E2E Test Authoring
Overview
Add end-to-end tests that exercise the Packmind CLI binary (dist/apps/cli/main.cjs) in realistic conditions. Tests run the actual CLI as a child process and, when authentication is needed, interact with a running API via HTTP gateways.
Test File Location
All spec files live in apps/cli-e2e-tests/src/ and follow the naming convention <command>.spec.ts.
Choosing a Test Wrapper
Two wrappers are available depending on whether the command requires authentication.
Unauthenticated commands — describeWithTempSpace
Provides an isolated temporary directory. No API required.
import { describeWithTempSpace, runCli } from './helpers';
describeWithTempSpace('my-command without auth', (getContext) => {
let result: Awaited<ReturnType<typeof runCli>>;
beforeEach(async () => {
const { testDir } = await getContext();
result = await runCli('my-command', { cwd: testDir });
});
it('exits with code 1', () => {
expect(result.returnCode).toBe(1);
});
it('shows an error message', () => {
expect(result.stdout).toContain('No credentials found');
});
});
Authenticated commands — describeWithUserSignedUp
Extends describeWithTempSpace by creating a real user account, signing in, and generating an API key. Requires a running API at http://localhost:4200.
import { describeWithUserSignedUp, runCli } from './helpers';
describeWithUserSignedUp('my-command with auth', (getContext) => {
let result: Awaited<ReturnType<typeof runCli>>;
beforeEach(async () => {
const { apiKey, testDir } = await getContext();
result = await runCli('my-command', { apiKey, cwd: testDir });
});
it('succeeds', () => {
expect(result.returnCode).toBe(0);
});
it('displays expected output', () => {
expect(result.stdout).toContain('Expected text');
});
});
The context object from describeWithUserSignedUp provides:
| Field | Description |
|---|---|
testDir |
Isolated temporary directory |
apiKey |
Valid API key for the created user |
user |
User object (email, etc.) |
organization |
Organization the user belongs to |
spaceId |
Global space ID for the organization |
gateway |
Authenticated gateway to call the API directly |
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.
- 2d ago First seen · 192 lines · 56 tokens per session scan A 04c70970c6fc
cli-e2e-test-authoring is a skill published in the GitHub repository PackmindHub/packmind (306 stars, last pushed 4d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,487 once invoked, about $0.0003 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
e2e-template-testing
End-to-end validation of coordinator and agent template changes.
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items.
winui-ui-testing
Automated UI testing for Windows desktop apps — generate a batch test script with the winapp ui UI Automation harness, run all tests in one pass, read results. Covers element assertions, interactions, value checking (TextBox, ComboBox, ToggleSwitch), keyboard shortcuts and typing (send-keys), hover, drag-and-drop…
comprehensive-testing
Complete testing strategy covering TDD workflow, test pyramid, unit/integration/E2E/property testing, framework best practices (Jest, Vitest, pytest), mock strategies, and CI integration. Use when writing tests, reviewing test quality, or establishing testing standards.
aidd-dev:05:test
Write and iterate on tests until they pass, and validate user journeys end-to-end in the browser.