Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/asmyshlyaev177/test-proxy-recordernpx agentmods add skills/asmyshlyaev177/test-proxy-recorder/tanstack-startWrote 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/asmyshlyaev177/test-proxy-recorder/tanstack-start)<a href="https://agentmods.dev/skills/asmyshlyaev177/test-proxy-recorder/tanstack-start"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/test-proxy-recorder/tanstack-start/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/asmyshlyaev177/test-proxy-recorder/tanstack-start"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/test-proxy-recorder/tanstack-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 275 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 282 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Server-Side Request Forgery · line 130 Code issues a request to a loopback, link-local, or private-range host. This can reach internal services not meant to be exposed and is a common SSRF pivot.Fix: Avoid requests to loopback/link-local/private hosts from skill code. If internal access is intended, document it and validate the target against an allowlist.
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.00194 | $0.02771 |
| Opus 5.5 | $0.00078 | $0.01108 |
| Sonnet 5.5 | $0.00039 | $0.00554 |
| Haiku 4.5 | $0.00019 | $0.00277 |
Grade A, and why
tanstack-start 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 yesterday.
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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill builds on test-proxy-recorder/proxy-setup. Read it first for the proxy CLI, playwright.config.ts, fixtures, and the record/replay lifecycle before applying TanStack Start patterns.
test-proxy-recorder — TanStack Start SSR
TanStack Start runs loaders and server functions on the server, so their fetch calls go through the proxy without a browser context — the same situation as Next.js SSR. The proxy correlates those requests to the right test session via the x-test-rcrd-id header. Playwright's playwrightProxy.before() already sets it on the browser navigation that triggers SSR, so the id arrives on the incoming server request — the one thing left is to attach it to outgoing server-side requests. Browser-only tests need none of this; the proxy falls back to the globally set session.
All helpers from test-proxy-recorder/tanstack-start are no-ops on the client and no-ops in production unless TEST_PROXY_RECORDER_ENABLED=true is set.
Record against a production build. Use
vite build+node .output/server/index.mjs(i.e.pnpm start), notvite dev. The dev server's per-request context differs from the production runtimeregisterProxyFetch()patches. Because the production server runs in production mode, setTEST_PROXY_RECORDER_ENABLED=trueon the app process for the e2e run.
Setup
Recommended — registerProxyFetch() in src/router.tsx
One line tags every server-side fetch — route loaders, server functions, server routes, and TanStack Query's queryFn during SSR prefetch. Call it at the top of src/router.tsx: that module runs on the server for every SSR request, and the call is idempotent, a no-op on the client, and a no-op in production unless the recorder is enabled.
// src/router.tsx
import { QueryClient } from '@tanstack/react-query';
import { createRouter } from '@tanstack/react-router';
import { registerProxyFetch } from 'test-proxy-recorder/tanstack-start';
import { routeTree } from './routeTree.gen';
registerProxyFetch(); // no-op on the client / in production unless TEST_PROXY_RECORDER_ENABLED=true
export function getRouter() {
const queryClient = new QueryClient();
return createRouter({ routeTree, context: { queryClient } });
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed 3d92807d2976
- 5d ago Changed 3f30122877a0
- 7d ago Changed 72a5cfb115a7
- 11d ago Changed · -61 lines 9c61be549b3a
- 1mo ago First seen · 305 lines · 194 tokens per session scan A 2a6a77801e81
tanstack-start is a skill published in the GitHub repository asmyshlyaev177/test-proxy-recorder (79 stars, last pushed yesterday), licensed MIT. It adds 194 tokens to every session and 2,771 once invoked, about $0.0008 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 skills, from other repositories
lastest
Lastest is a visual regression testing platform. It records browser tests, runs them via Playwright, diffs screenshots, and uses AI to classify changes. Available as an MCP server for AI agent integration.
nextjs-testing
Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
playwright-trace
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).