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 rules/rm2thaddeus/pixel_detective/ux-workflow-patternsgit clone --depth 1 https://github.com/rm2thaddeus/Pixel_DetectiveWhat 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.00000 | $0.04616 |
| Opus 5 | $0.00000 | $0.02308 |
| Sonnet 5 | $0.00000 | $0.00923 |
| Haiku 4.5 | $0.00000 | $0.00462 |
Grade A, and why
ux-workflow-patterns 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 — 678 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Workflow Patterns
🎯 USER EXPERIENCE PATTERNS (From Sprint 10 UX Lessons)
Based on critical UX discoveries, user feedback, and workflow improvements implemented during Sprint 10.
🚨 CRITICAL UX FLAW DISCOVERED & FIXED
The "Add Images" Workflow Disaster
// ❌ CRITICAL UX FLAW: Browser security violation
function AddImagesModal() {
const [directoryPath, setDirectoryPath] = useState('')
return (
<Modal>
<ModalBody>
<Text>Enter the directory path containing your images:</Text>
<Input
placeholder="C:\Users\username\Pictures\..."
value={directoryPath}
onChange={(e) => setDirectoryPath(e.target.value)}
/>
<Button onClick={() => processDirectory(directoryPath)}>
Process Directory
</Button>
</ModalBody>
</Modal>
)
}
Why this was a disaster:
- Security Violation: Browsers cannot access local file system paths
- 100% Failure Rate: This workflow would fail for every user
- Confusing UX: Users don't understand why it doesn't work
- Backend Mismatch: Backend expects server paths, not client paths
✅ SOLUTION: Proper File Upload Workflow
// ✅ CORRECT: Browser-compatible file upload
function AddImagesModal() {
const [selectedFiles, setSelectedFiles] = useState<FileList | null>(null)
const fileInputRef = useRef<HTMLInputElement>(null)
const handleFolderSelect = (event: React.ChangeEvent<HTMLInputElement>) => {
if (event.target.files) {
setSelectedFiles(event.target.files)
}
}
const handleUpload = async () => {
if (!selectedFiles) return
const formData = new FormData()
Array.from(selectedFiles).forEach(file => {
formData.append('files', file)
})
const response = await api.post('/api/v1/ingest/upload', formData, {
headers: { 'Content-Type': 'multipart/form-data' }
})
// Navigate to job tracking
router.push(`/logs/${response.data.job_id}`)
}
return (
<Modal>
<ModalBody>
<VStack spacing={4}>
<Text>Select a folder containing your images:</Text>
<Box
p={6}
border="2px dashed"
borderColor="gray.300"
borderRadius="md"
cursor="pointer"
onClick={() => fileInputRef.current?.click()}
_hover={{ bg: 'gray.50' }}
>
<VStack>
<Icon as={FiUploadCloud} boxSize={12} color="gray.500" />
<Text fontWeight="medium">Click to select a folder</Text>
<Text fontSize="sm" color="gray.500">
Files will be uploaded to the server for processing
</Text>
</VStack>
</Box>
<Input
type="file"
ref={fileInputRef}
onChange={handleFolderSelect}
style={{ display: 'none' }}
{...{ webkitdirectory: 'true', mozdirectory: 'true' }}
/>
{selectedFiles && (
<Alert status="success">
<AlertIcon />
<Text>{selectedFiles.length} files selected</Text>
</Alert>
)}
</VStack>
</ModalBody>
<ModalFooter>
<Button
colorScheme="blue"
onClick={handleUpload}
isDisabled={!selectedFiles}
>
Upload and Process
</Button>
</ModalFooter>
</Modal>
)
}
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 · 678 lines · 0 tokens per session scan A 9ca576383514
ux-workflow-patterns is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,616 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
modus-angular-icon-names
Complete list of valid Modus icon names for Angular applications.
svg-check
Apply when editing, generating, or reviewing any SVG diagram. Pixel-perfect Playwright bbox-check is the acceptance test — eyeballing is not sufficient. Run on every SVG before declaring done.
oiloil-ui-ux-guide
Shared instructions for maintaining modern-ui-ux-review.
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.