Borrowing it
Nothing to install: this file belongs to Innei/Kagura. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Innei/Kagura/main/.claude/skills/writing-live-e2e-tests/SKILL.mdgit clone --depth 1 https://github.com/Innei/KaguraWrote 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/innei/kagura/writing-live-e2e-tests)<a href="https://agentmods.dev/skills/innei/kagura/writing-live-e2e-tests"><img src="https://agentmods.dev/badge/skills/innei/kagura/writing-live-e2e-tests/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/innei/kagura/writing-live-e2e-tests"><img src="https://agentmods.dev/badge/skills/innei/kagura/writing-live-e2e-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 117 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00073 | $0.02372 |
| Opus 5 | $0.00036 | $0.01186 |
| Sonnet 5 | $0.00015 | $0.00474 |
| Haiku 4.5 | $0.00007 | $0.00237 |
Grade A, and why
writing-live-e2e-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 11d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Live E2E Tests
Overview
Live E2E tests run against a real Slack workspace via Socket Mode. Each test is a standalone run-*.ts file in src/e2e/live/ that exports a LiveE2EScenario object. The CLI auto-discovers and runs them.
When the user asks to add a live E2E test, implement the scenario and run the local validation commands. When they ask to "跑下" or run it and .env.e2e exists, run the real live scenario too.
Skeleton
Every scenario file follows this structure:
import './load-e2e-env.js';
import { randomUUID } from 'node:crypto';
import fs from 'node:fs/promises';
import path from 'node:path';
import { createApplication } from '~/application.js';
import { env } from '~/env/server.js';
import type { LiveE2EScenario } from './scenario.js';
import { runDirectly } from './scenario.js';
import { SlackApiClient } from './slack-api-client.js';
interface MyResult {
botUserId: string;
channelId: string;
failureMessage?: string;
matched: {
/* booleans for each assertion */
};
passed: boolean;
rootMessageTs?: string;
runId: string;
}
async function main(): Promise<void> {
// 1. Guard env
if (!env.SLACK_E2E_ENABLED) throw new Error('...');
if (!env.SLACK_E2E_CHANNEL_ID || !env.SLACK_E2E_TRIGGER_USER_TOKEN) throw new Error('...');
// 2. Setup
const runId = randomUUID();
const triggerClient = new SlackApiClient(env.SLACK_E2E_TRIGGER_USER_TOKEN);
const botClient = new SlackApiClient(env.SLACK_BOT_TOKEN);
const botIdentity = await botClient.authTest();
// 3. Init result object with all matched: false
const result: MyResult = {
/* ... */
};
// 4. Start application
const application = createApplication();
let caughtError: unknown;
try {
await application.start();
await delay(3_000);
// 5. Post trigger message with runId marker
// 6. Poll with deadline loop
// 7. Assert via assertResult()
// 8. Set result.passed = true AFTER assertion passes
await writeResult(result);
assertResult(result);
result.passed = true;
await writeResult(result);
} catch (error) {
result.failureMessage = error instanceof Error ? error.message : String(error);
caughtError = error;
} finally {
await writeResult(result).catch(() => {});
await application.stop().catch(() => {});
}
if (caughtError) throw caughtError;
}
// ALWAYS use env.SLACK_E2E_RESULT_PATH with .replace()
async function writeResult(result: MyResult): Promise<void> {
const resultPath = env.SLACK_E2E_RESULT_PATH.replace(/result\.json$/, 'my-test-result.json');
const absolutePath = path.resolve(process.cwd(), resultPath);
await fs.mkdir(path.dirname(absolutePath), { recursive: true });
await fs.writeFile(absolutePath, `${JSON.stringify(result, null, 2)}\n`, 'utf8');
}
function assertResult(result: MyResult): void {
const failures: string[] = [];
// Push descriptive failure strings
if (failures.length > 0) throw new Error(`E2E failed: ${failures.join('; ')}`);
}
function delay(ms: number): Promise<void> {
return new Promise((resolve) => {
setTimeout(resolve, ms);
});
}
export const scenario: LiveE2EScenario = {
id: 'kebab-case-id',
title: 'Human Readable Title',
description: 'One sentence describing what is verified.',
keywords: ['searchable', 'terms'],
run: main,
};
runDirectly(scenario);
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.
- 11d ago First seen · 245 lines · 73 tokens per session scan A d74fa6d2cf74
writing-live-e2e-tests is a skill published in the GitHub repository Innei/Kagura (52 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 2,372 once invoked, about $0.0004 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-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
qa-testing-playwright
Builds and debugs Playwright E2E suites. Use when authoring browser tests, fixing flakes, or hardening Playwright CI and locator strategy.