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 bishopZ/2026-Boilerplate --skill migrate-api-to-tanstack-querygit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWrote 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/bishopz/2026-boilerplate/migrate-api-to-tanstack-query)<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/migrate-api-to-tanstack-query"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-api-to-tanstack-query/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/bishopz/2026-boilerplate/migrate-api-to-tanstack-query"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/migrate-api-to-tanstack-query.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.00032 | $0.00543 |
| Opus 5.5 | $0.00013 | $0.00217 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
migrate-api-to-tanstack-query 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate API to TanStack Query
Use this skill when the task is to introduce TanStack Query for REST data fetching/caching without rewriting the backend.
Goal
Move client-side server-state logic from ad hoc calls to TanStack Query while preserving existing API behavior and auth guarantees.
Preconditions
- Keep API contracts stable while migrating (
/api/*endpoints first). - For auth/session flows, prefer JSON endpoints (
POST /api/session,DELETE /api/session) rather than redirect-based legacy endpoints. - Keep route protection and cookie auth behavior unchanged unless explicitly requested.
Files To Update
1) Dependencies and scripts (package.json)
- Add
@tanstack/react-query. - Add
@tanstack/react-query-devtoolsonly if requested.
2) Query client setup
- Add a shared query client module under
src/client/(for example:src/client/data/query-client.ts). - Wire
QueryClientProviderinsrc/client/main.tsx. - Keep provider order stable with Redux, i18n, and Chakra providers.
3) API access layer
- Create or update an API module under
src/client/utilities/orsrc/client/data/with typed fetch helpers. - Normalize request/response/error handling in one place.
- Use resource-oriented functions (
createSession,deleteSession,getEncryptionKey) instead of endpoint-shaped function names.
4) Feature migration
- Replace one feature at a time with
useQuery/useMutation. - Add targeted cache invalidation where state changes occur.
- Keep form/UI behavior unchanged while moving data logic.
5) Docs and changelog
- Update
docs/API.mdwhen endpoint usage guidance changes. - Update
docs/TECHNOLOGY.mdif TanStack Query becomes part of the default stack. - Add migration notes under
CHANGELOG.md→Unreleased.
Validation Checklist
- Run
npm run lint - Run
npm run type-check - Run targeted E2E tests for migrated flows (for example
playwright/e2e/auth/login.spec.ts) - Verify no direct feature code still calls
fetchfor the migrated paths
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 · 64 lines · 32 tokens per session scan A d1404962c9e7
migrate-api-to-tanstack-query is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 543 once invoked, about $0.0001 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
github-review-iteration
Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating until actionable review items are cleared. Use when the user says “address PR review”, “triage review comments”, or “iterate until review is clean”.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.