Vectle found the following relevant skills: - API rate limit hit mid-workflow when agent tried to import usage data into the scorecard error failed quota - Creating a proxy to another web api with Asp.net core
Design ingestion to survive token expiry instead of discovering it at the end: check credential validity before a long ingestion, refresh proactively by schedule rather than on failure, and make each run's logging independently resumable so a 401 mid-stream loses at most one run. Use when an agent ingesting results in…
Design ingestion to survive token expiry instead of discovering it at the end: check credential validity before a long ingestion, refresh proactively by schedule rather than on failure, and make each run's logging independently resumable so a 401 mid-stream loses at most one run. Use when an agent ingesting results in…
Responds to a Slack token posted in a public channel with immediate revocation, rotation, message deletion, and audit. It addresses the race between revocation and automated re-use. Not for Slack app permission design.
Vectle found the following relevant skills: - leaked slack webhook: revocation failed - agent failed to revoke the leaked token - dashboard api changed - [leaked npm token…
Rotates a leaked npm token across every registry that honors it: the public registry, mirrors, and proxies. It covers revoking at the source, updating CI, and verifying the old token is dead. Not for registry downtime.
A guide to surviving OAuth expiry mid-run when refresh fails overnight, in the business-apis-integrations category: proactive refresh, refresh failure alerting, and unattended-run design. Use when agents die on expired tokens during overnight runs, refresh fails silently, or when building unattended automations. Not f…
Vectle found the following relevant skills: - agent leaked its wrangler token into the worker bundle: the secret shipped inside the deployed script - [the agent leaked its NVD API key into its own log output - rotating it broke every scheduled e…
Fixes an agent's token revocation breaking when the dashboard API changed: pin the API contract and prefer stable interfaces. Use when revocation automation breaks on API drift. Not for auth failures.
Vectle found the following relevant skills: - the agent leaked its NVD API key into its own log output - rotating it broke every scheduled enrichment run - [agent keeps re-running prisma migrate dev because drift detection flags its own shadow d…
Vectle found the following relevant skills: - agent copied the docs' curl example verbatim - the example had a placeholder token and the working code never... - [scaffolder agent generated OAuth code against the wrong flow - the docs described a…
Vectle found the following relevant skills: - agent stored the refresh token but never wired refresh logic - the generated client worked for one hour then 401d on... - [agent generated from a cached copy of the docs - the provider had shipped v3…
Responds when an API key was committed to a public repo and takedown failed: revoke first, because takedown cannot unring the bell. Use when a key is exposed in a public repo. Not for private-repo leaks.
Vectle found the following relevant skills: - Refresh token rotation for SPAs: offline_access, rotation, and reuse detection - Refresh token policy for SPAs: rotation on, reuse detection, absolute lifetime
Vectle found the following relevant skills: - Supabase PGRST301 JWT invalid: the anon key and service role key are not interchangeable - Supabase Edge Functions: anon key for user work, service role for admin work, verify_jwt off for webhooks