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 skills add atman-33/workhub --skill react-router-v7-appgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/react-router-v7-app)<a href="https://agentmods.dev/skills/atman-33/workhub/react-router-v7-app"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/react-router-v7-app/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/atman-33/workhub/react-router-v7-app"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/react-router-v7-app.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.00046 | $0.01463 |
| Opus 5.5 | $0.00018 | $0.00585 |
| Sonnet 5.5 | $0.00009 | $0.00293 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
react-router-v7-app 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Router v7 App Implementation
1. Route Structure
- Use file-based routing in
app/routes/. - Route files:
route.tsxfor route components. - Prefer folder routes like
users.$id/route.tsxwhen a route needs colocated helpers, components, or tests; sibling files in the folder do not become routes. - If tests live under
app/routes/, configureflatRoutes({ ignoredRouteFiles: [...] })to exclude*.test.*and*.spec.*from route discovery. - Use underscore prefix for route groups:
_app,_landing. - Use dot notation for nested routes:
users.$id.tsx.
2. Data Loading Patterns
- Use
loaderfunctions for server-side data fetching. - Use
actionfunctions for form submissions and mutations. - Leverage
useLoaderData()anduseActionData()hooks. - Handle loading states with
useNavigation().
3. Route Component Structure
Use arrow functions for all exports.
import type { Route } from './+types/route';
export const loader = async ({ request, params, context }: Route.LoaderArgs) => {
// Server-side data loading
// Return an object
return { ... };
};
export const action = async ({ request, params, context }: Route.ActionArgs) => {
// Handle form submissions and mutations
// Return an object
return { ... };
};
const Page = ({ loaderData, actionData }: Route.ComponentProps) => {
// Component implementation with typed props
return (
<div>
{/* Content */}
</div>
);
};
export default Page;
4. Error Handling
- Use
ErrorBoundarycomponents for route-level error handling. - Implement proper error responses in loaders/actions.
- Use
isRouteErrorResponse()for typed error handling.
5. Meta and Headers
- Export
metafunction for dynamic page metadata. - Export
headersfunction for custom HTTP headers. - Use proper SEO practices with meta tags.
6. Project Structure
The app folder should follow this structure:
public # Static files (images, fonts, etc.)
|
app
|
+-- components # Shared components
|
+-- config # Global configuration and environment variables
|
+-- constants # Global constants
|
+-- hooks # Shared hooks
|
+-- lib # Pre-configured reusable libraries
|
+-- routes # React Router routing directory
|
+-- stores # Global state stores
|
+-- testing # Test utilities and mock servers
|
+-- types # Base types used across the application
|
+-- utils # Shared utility functions
|
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 · 206 lines · 46 tokens per session scan A 3079de32f6d2
react-router-v7-app is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,463 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
add-localization
Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
pcf
Builds, tests, diagnoses, upgrades, deploys and verifies Power Apps component framework (PCF) code components for model-driven apps and Power Pages — field and dataset controls, standard and virtual (React) — from Microsoft-maintained templates and recipes pinned to a tested version matrix. Runs quality gates…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.