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.
git clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWrote 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/rules/kubev2v/forklift-console-plugin/testing)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/testing"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/testing/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/rules/kubev2v/forklift-console-plugin/testing"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/testing.svg" alt="Reviewed on agentmods" width="80" 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.01596 |
| Opus 5.5 | $0.00000 | $0.00638 |
| Sonnet 5.5 | $0.00000 | $0.00319 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
testing 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 10d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Guidelines (Supplement)
For basic testing approach (Jest for unit, Playwright for E2E), see AGENTS.md. This rule adds detailed patterns and coverage policy (MTV-6267).
1. Unit Tests (Jest)
File Location
- Place test files in
__tests__folder adjacent to the module being tested - Naming:
ComponentName.test.tsxorutilName.test.ts
Structure
import { render, screen } from '@testing-library/react';
import { userEvent } from '@testing-library/user-event';
describe('ComponentName', () => {
it('renders correctly with valid props', () => {
render(<Component {...defaultProps} />);
expect(screen.getByText('Expected text')).toBeInTheDocument();
});
it('handles user interactions', async () => {
const user = userEvent.setup();
render(<Component {...defaultProps} />);
await user.click(screen.getByRole('button'));
await user.type(screen.getByLabelText('Name'), 'test-value');
expect(screen.getByDisplayValue('test-value')).toBeInTheDocument();
});
it('handles loading state', () => {
render(<Component loaded={false} />);
expect(screen.getByRole('progressbar')).toBeInTheDocument();
});
it('handles error state', () => {
render(<Component loadError={new Error('Failed')} />);
expect(screen.getByText(/failed/i)).toBeInTheDocument();
});
it('handles empty state', () => {
render(<Component data={[]} />);
expect(screen.getByText(/no items/i)).toBeInTheDocument();
});
});
Mocking
// Mock i18n
jest.mock('src/utils/i18n', () => ({
useForkliftTranslation: () => ({ t: (key: string) => key }),
}));
// Mock Console SDK
jest.mock('@openshift-console/dynamic-plugin-sdk', () => ({
useK8sWatchResource: jest.fn(),
}));
What to Test
- Renders without error
- Displays correct data
- Handles loading, error, empty states
- User interactions trigger correct callbacks
- Edge cases (null data, empty arrays, boundary values)
Run Commands
npm test # Run all unit tests
npm run test:coverage # With coverage report
npm test path/to/file.test.ts # Run specific test file
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.
- 10d ago Changed a064814f2f42
- 17d ago Changed · +4 lines e657a188696f
- 1mo ago Changed · +23 lines bb1070ee8537
- 1mo ago First seen · 164 lines · 0 tokens per session scan A fa5c4664a3dc
testing is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,596 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 cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
tester
Tester role - Unit, E2E, and visual regression testing.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.