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 skills/trpc/trpc/non-json-content-typesnpx skills add trpc/trpc --skill non-json-content-typesgit clone --depth 1 https://github.com/trpc/trpcWhat 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.00075 | $0.01609 |
| Opus 5 | $0.00037 | $0.00805 |
| Sonnet 5 | $0.00015 | $0.00322 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
non-json-content-types 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 3d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tRPC -- Non-JSON Content Types
Setup
Server:
// server/trpc.ts
import { initTRPC } from '@trpc/server';
const t = initTRPC.create();
export const router = t.router;
export const publicProcedure = t.procedure;
// server/appRouter.ts
import { octetInputParser } from '@trpc/server/http';
import { z } from 'zod';
import { publicProcedure, router } from './trpc';
export const appRouter = router({
uploadForm: publicProcedure
.input(z.instanceof(FormData))
.mutation(({ input }) => {
const name = input.get('name');
return { greeting: `Hello ${name}` };
}),
uploadFile: publicProcedure.input(octetInputParser).mutation(({ input }) => {
// input is a ReadableStream
return { valid: true };
}),
});
export type AppRouter = typeof appRouter;
Client:
// client/index.ts
import {
createTRPCClient,
httpBatchLink,
httpLink,
isNonJsonSerializable,
splitLink,
} from '@trpc/client';
import type { AppRouter } from '../server/appRouter';
const url = 'http://localhost:3000';
const trpc = createTRPCClient<AppRouter>({
links: [
splitLink({
condition: (op) => isNonJsonSerializable(op.input),
true: httpLink({ url }),
false: httpBatchLink({ url }),
}),
],
});
Core Patterns
FormData mutation
// server/appRouter.ts
import { z } from 'zod';
import { publicProcedure, router } from './trpc';
export const appRouter = router({
createPost: publicProcedure
.input(z.instanceof(FormData))
.mutation(({ input }) => {
const title = input.get('title') as string;
const body = input.get('body') as string;
return { id: '1', title, body };
}),
});
// client usage
const form = new FormData();
form.append('title', 'Hello');
form.append('body', 'World');
const result = await trpc.createPost.mutate(form);
Binary file upload with octetInputParser
// server/appRouter.ts
import { octetInputParser } from '@trpc/server/http';
import { publicProcedure, router } from './trpc';
export const appRouter = router({
upload: publicProcedure
.input(octetInputParser)
.mutation(async ({ input }) => {
const reader = input.getReader();
let totalBytes = 0;
while (true) {
const { done, value } = await reader.read();
if (done) break;
totalBytes += value.byteLength;
}
return { totalBytes };
}),
});
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.
- 3d ago First seen · 266 lines · 75 tokens per session scan A a9b9b9f40060
non-json-content-types is a skill published in the GitHub repository trpc/trpc (40,567 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 1,609 once invoked, about $0.0004 per session on Opus 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 skills, from other repositories
portaljs-connect-ckan
Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static…
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
create-pr
Create and complete GitHub pull requests. Use when the user asks to create, open, raise, or publish a PR; finish changes as a PR; monitor or babysit an existing PR; wait for review bots; or address PR review feedback and check failures. Covers review, safe commits and metadata, PR creation, exact-commit monitoring…
fullstack-workflow
Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.
review
Review code changes, auto-fix safe issues, and report bugs.
llm
Guidelines for implementing LLM (Language Model) functionality in the application.