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 Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill tanstack-integrationgit clone --depth 1 https://github.com/Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrationsWrote 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/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tanstack-integration)<a href="https://agentmods.dev/skills/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tanstack-integration"><img src="https://agentmods.dev/badge/skills/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tanstack-integration/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/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tanstack-integration"><img src="https://agentmods.dev/badge/skills/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tanstack-integration.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.00042 | $0.01734 |
| Opus 5 | $0.00021 | $0.00867 |
| Sonnet 5 | $0.00008 | $0.00347 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
tanstack-integration 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 12d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 12d ago First seen · 282 lines · 42 tokens per session scan A 7a8ed88f8e02
tanstack-integration is a skill published in the GitHub repository Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations (73 stars, last pushed 6d ago), with no licence file. It adds 42 tokens to every session and 1,734 once invoked, about $0.0002 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
loom-react
Modern client-side React development patterns.
loom-accessibility
Web accessibility patterns, WCAG compliance, and inclusive design.
Accessibility Checklist
A concrete, checklist-driven pass for semantic HTML, ARIA, keyboard navigation, contrast, alt text, and focus management.
Visual Verification Workflow
The procedure for actually confirming a UI change in a real or preview browser — golden path, an edge case, console errors, and responsive/dark-mode checks — before calling it done.
Component Conventions
Guidance on composing, naming, and sizing components, designing their props, and keeping their state as local as possible.
Contract-First Development
How to define, document, and maintain the shared contract between frontend and backend.