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/react-components)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/react-components"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/react-components/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/react-components"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/react-components.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.01304 |
| Opus 5.5 | $0.00000 | $0.00522 |
| Sonnet 5.5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
react-components 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 1mo 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Component Patterns (Supplement)
For core React conventions (functional components, FC type, imports, hooks rules), see AGENTS.md. This rule adds PatternFly and Console SDK patterns.
1. PatternFly Component Usage
Use Enums for Variants
import { Button, ButtonVariant } from '@patternfly/react-core';
// Always use enum, not string literal
<Button variant={ButtonVariant.primary}>Save</Button>
<Button variant={ButtonVariant.link}>Cancel</Button>
Custom Select Component
Always use the project's custom Select wrapper for consistency:
import Select from '@components/common/Select';
// NOT: import { Select } from '@patternfly/react-core';
Use PF_LABEL_STATUS for Status Props
Use the shared constants instead of string literals for PatternFly status props:
import { PF_LABEL_STATUS, type PfLabelStatus } from '@utils/constants';
// ✅ Good
<Label status={PF_LABEL_STATUS.DANGER}>Error</Label>
<Icon status={PF_LABEL_STATUS.WARNING}>...</Icon>
// ❌ Bad
<Label status="danger">Error</Label>
Use STATUS_ICONS for Status Icons
Use the shared status icon map instead of manually wrapping icons with hardcoded colors:
import { STATUS_ICONS } from '@components/status/statusIcons';
// ✅ Good - uses PF6 Icon status prop, respects theming
{STATUS_ICONS.danger}
{STATUS_ICONS.warning}
// ❌ Bad - hardcoded hex colors break in dark mode
<ExclamationCircleIcon color="#C9190B" />
Common PatternFly Patterns
import {
Alert,
AlertVariant,
EmptyState,
EmptyStateVariant,
Spinner,
Title,
} from '@patternfly/react-core';
2. Console SDK Integration
Watching Resources
import { useK8sWatchResource } from '@utils/hooks/useK8sWatchResource';
const [providers, loaded, error] = useK8sWatchResource<V1beta1Provider[]>({
groupVersionKind: ProviderModelGroupVersionKind,
isList: true,
namespaced: true,
namespace,
});
Resource Operations
import { k8sCreate, k8sUpdate, k8sDelete, k8sPatch } from '@openshift-console/dynamic-plugin-sdk';
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.
- 1mo ago First seen · 202 lines · 0 tokens per session scan A abf54fb0d8fe
react-components 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,304 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
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
tanstack-react-router_routing
TanStack Router: Routing.
project-structure
Folder layout for Next.js App Router and Vite + React variants.