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/PackmindHub/packmindWrote 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/packmindhub/packmind/standard-frontend-data-flow)<a href="https://agentmods.dev/rules/packmindhub/packmind/standard-frontend-data-flow"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-frontend-data-flow/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/packmindhub/packmind/standard-frontend-data-flow"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-frontend-data-flow.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.00452 | $0.00452 |
| Opus 5.5 | $0.00181 | $0.00181 |
| Sonnet 5.5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
standard-frontend-data-flow 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 24d 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.
What it actually says
Standard: Frontend Data Flow
This standard defines the recommended data flow pattern for frontend routes in the Packmind codebase using React Router v7 in framework mode with TanStack Query for data management. It ensures consist... :
- Access data via query or mutation hooks in frontend route modules rather than calling gateways directly to maintain separation between data access and presentation layers
- Consume data in route module components using the useLoaderData() hook to access data returned by the clientLoader
- Define a crumb property in the handle export of route modules to enable automatic navigation breadcrumb generation
- Enable query options conditionally using the enabled property to prevent execution when required parameters are missing or invalid
- Export query hooks (e.g., useGetStandardByIdQuery) alongside query options to provide consistent component-level data access patterns
- Export query options as standalone functions (e.g., getStandardByIdOptions) separate from hooks to enable reuse in both hooks and route loaders
- Leave
retryto the sharedshouldRetryTransientpolicy; never retry a 4xx, as only network failures and 5xx are retried, once - Name route module default export functions with a suffix of RouteModule (e.g., StandardDetailRouteModule) to clearly identify route-level components
- Prefer
queryClient.ensureQueryData()overqueryClient.fetchQuery()in clientLoaders to return cached data when available instead of always fetching - Store domain queries in the domain folder organized by entity at apps/frontend/src/domain/{entity}/api/queries/ to maintain clear separation of concerns and domain boundaries
- Use clientLoader function (not loader) in route modules for data fetching when using React Router in SPA mode to ensure proper client-side data loading
- Use Gateway type helper for authenticated operations or PublicGateway for public operations in frontend gateway interfaces to ensure proper command/response typing
- Use queryClient.ensureQueryData() or queryClient.fetchQuery() in clientLoader to preload data before rendering and leverage TanStack Query's caching mechanisms
Full standard is available here for further request: Frontend Data Flow
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.
- 24d ago Changed · +1 lines · +36 tokens per session 703a555e46f1
- 1mo ago First seen · 20 lines · 416 tokens per session scan A b0d938732100
standard-frontend-data-flow is a cursor rule published in the GitHub repository PackmindHub/packmind (319 stars, last pushed yesterday), licensed Apache-2.0. It adds 452 tokens to every session, about $0.0018 per session on Opus 5.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 cursor rules, from other repositories
core
Core architecture and quality rules for React + Vite + shadcn/ui template.
project
Core project context for ai-context-kit.
project-spine-apps-web
Project Spine scoped guidance for "apps/web".
cursorrules
Cursor rule "cursorrules" from googlarz/agents-sync, covering .cursorrules — managed by agents-sync v1.0.0, language: typescript / next.js 14 and run tests: npm test.
react-development
Developing React components in Astro application.
react
React and TypeScript conventions for the frontend.