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 G1Joshi/Agent-Skills --skill remixgit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/remix)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/remix"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/remix/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/g1joshi/agent-skills/remix"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/remix.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.00040 | $0.01487 |
| Opus 5.5 | $0.00016 | $0.00595 |
| Sonnet 5.5 | $0.00008 | $0.00297 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
remix 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 23d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remix
Remix is a full-stack web framework built on web standards (Fetch API, Request/Response), providing nested routing, resilient form mutations, and seamless Vite integration.
When to Use
- Web Standards-First Full-Stack Applications: Utilizing standard
Request,Response, and HTML forms via Remix / React Router v7. - High-Performance Server-Rendered Applications: Instant page transitions with nested routing and parallel data loading.
- Resilient Web Apps with Progressive Enhancement: Applications that function reliably before JavaScript has loaded.
- Optimistic UI & Mutation Heavy Interfaces: Using
useFetcherand server actions without bespoke client state machines.
Quick Start
import { json } from "@remix-run/node";
import { useLoaderData, Form } from "@remix-run/react";
// Functions run on server
export async function loader() {
return json(await db.getTasks());
}
export async function action({ request }) {
const formData = await request.formData();
await db.createTask(formData.get("title"));
return json({ ok: true });
}
// Component runs on Client + Server
export default function Tasks() {
const tasks = useLoaderData<typeof loader>();
return (
<Form method="post">
<input name="title" />
<button>Add</button>
</Form>
);
}
Core Concepts
Nested Routing & Parallel Loader Data Loading
Fetching server-side data per route segment in parallel:
// app/routes/users.$id.tsx
import { json, type LoaderFunctionArgs } from "@remix-run/node";
import { useLoaderData, Link } from "@remix-run/react";
export async function loader({ params }: LoaderFunctionArgs) {
const userId = params.id;
const user = await db.user.findUnique({ where: { id: userId } });
if (!user) {
throw new Response("User Not Found", { status: 404 });
}
return json({ user });
}
export default function UserDetailRoute() {
const { user } = useLoaderData<typeof loader>();
return (
<div className="user-card">
<h2>{user.name}</h2>
<p>{user.email}</p>
<Link to="edit">Edit Profile</Link>
</div>
);
}
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.
- 23d ago Changed · +5 lines 0f6ed883626c
- 27d ago Changed · +135 lines · +20 tokens per session 7f2d582d95c2
- 1mo ago First seen · 74 lines · 20 tokens per session scan A 0f0d0cd7897a
remix is a skill published in the GitHub repository G1Joshi/Agent-Skills (15 stars, last pushed 24d ago), licensed MIT. It adds 40 tokens to every session and 1,487 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
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
api-design
Design stable, versioned, self-documenting APIs. Easy to use correctly, hard to use incorrectly. Apply Hyrum's Law from day one.
api-and-interface-design
Guidance for designing stable, clearly documented interfaces between software parts, such as web APIs, GraphQL schemas, modules, and component properties. It covers defining the contract first, limiting accidental dependencies, and planning safe changes.
deprecation-and-migration
A guide for retiring old code, systems, or interfaces and moving users to replacements. Deprecation means marking something as no longer preferred; migration means switching its users safely.
awesome-performance-audit
Read-only performance and reliability audit: event loop, backpressure, memory and CPU, timeouts, retries, queues, Core Web Vitals, bundles, with a verdict. Use when something is slow, memory climbs or latency spikes.
awesome-api-design
Designs or reviews an HTTP API's shape before code: resources, versioning, pagination, idempotency, filtering. Use when asked to design an API or an endpoint.