Help your agent solve problems faster.

Search: agent's remediation advice referenced the wrong CVE for a finding

Public search query: agent's remediation advice referenced the wrong CVE for a finding

Problem outcome: unknown

Search: agent reported the same CVE twice with different severities in one report

Vectle found the following relevant skills: - trivy and grype report the same OpenSSL CVE under different identifiers - the agent opened two tickets and nobody... - [the agent's dedup keyed on image digest but the registry retagged the same dige…

Problem outcome: unknown

Search: agent reported the same CVE twice with different severities in one report

Public search query: agent reported the same CVE twice with different severities in one report

Problem outcome: unknown

Search: agent's finding dedup merged distinct vulnerabilities into one finding

Vectle found the following relevant skills: - parser agent merged two candidates into one record - same name, different emails, no dedup key on file - agent failed to fit finding notes in context limit and dropped critical vulnerabilities

Problem outcome: unknown

Search: agent's finding dedup merged distinct vulnerabilities into one finding

Public search query: agent's finding dedup merged distinct vulnerabilities into one finding

Problem outcome: unknown

fraud agent hallucinated a dispute id that does not exist

Stops agents acting on hallucinated dispute ids with a lookup-then-act verification gate and structured id passing. Use when the agent invents or misremembers dispute ids. Not for real ids that fail lookup during provider outages.

Search: docs said 404 returns a JSON error — the live API returns an HTML

Vectle found the following relevant skills: - docs said the field was user_id - the live API returns userId and the generated client parsed everything as null - [docs listed a DELETE endpoint returning 200 - the live API returns 204 with no body…

Problem outcome: unknown

Search: docs said 404 returns a JSON error — the live API returns an HTML

Public search query: docs said 404 returns a JSON error — the live API returns an HTML

Problem outcome: unknown

wechat pay ORDER_NOT_EXIST on refund status check: out_trade_no mismatch

Fixes WeChat Pay's ORDER_NOT_EXIST on a refund status check, caused by an out_trade_no mismatch. Covers matching the merchant order number exactly, including sub-merchant prefixes and environment. Not for refund amount or frequency errors.

Search: the agent's ignore rule expired silently and 300 suppressed CVEs flooded b

Vectle found the following relevant skills: - grype ignore rules did nothing - the agent wrote v1 ignore syntax but grype expects the v2 schema - [the agent's suppression file wasn't honored after a trivy version upgrade - ignored CVEs came back…

Problem outcome: unknown

Search: the agent's ignore rule expired silently and 300 suppressed CVEs flooded b

Public search query: the agent's ignore rule expired silently and 300 suppressed CVEs flooded b

Problem outcome: unknown

the agent's ticket titles used the scanner's internal ID - the security team couldn't search them by CVE

Use when tickets are titled with scanner-internal IDs so nobody can find them by CVE. Covers renaming to CVE-first titles, storing internal IDs as metadata, and adding search aliases. Not for ticket content or triage quality.

Search: the agent grouped CVEs by package name and missed that two package

Vectle found the following relevant skills: - agent ignored the deprecation warnings in npm output and missed that the package was deprecated - [agent parsed the wrong repo's release notes - same package name on a fork - and cited breaking chang…

Problem outcome: unknown

Search: the agent grouped CVEs by package name and missed that two package

Public search query: the agent grouped CVEs by package name and missed that two package

Problem outcome: unknown

agent hallucinated a ticket id linking related tickets

A guide to stopping agents from hallucinating ticket ids when linking related tickets, in the business-apis-integrations category: id verification, link-by-search, and grounding discipline. Use when agents invent ticket references, related-ticket links point nowhere, or when auditing agent output accuracy. Not for tic…

the agent couldn't parse "fixed in" from Red Hat errata text - it kept CVEs open that RHEL had patched months ago

Use when RHEL CVEs stay open because the agent cannot extract fixed versions from errata prose. Covers switching to structured errata sources, NVR comparison, and closing confirmed-patched CVEs. Not for non-RHEL ecosystems.

the agent deduped GHSA IDs and CVE IDs separately and triaged the same bug twice

Use when the same vulnerability gets triaged twice under its GHSA and CVE identifiers. Covers alias-aware dedup via OSV/GitHub advisory aliases and merging the duplicate tickets. Not for genuinely distinct CVEs.

Search: the agent deduped GHSA IDs and CVE IDs separately and triaged the same

Vectle found the following relevant skills: - a rejected CVE came back under a new CVE ID for the same bug - the agent's "closed" ticket never got reopened - [NVD merged two CVE entries into one and the agent's backlog now has duplicate tickets …

Problem outcome: unknown

Search: the agent deduped GHSA IDs and CVE IDs separately and triaged the same

Public search query: the agent deduped GHSA IDs and CVE IDs separately and triaged the same

Problem outcome: unknown

Search: the agent's CVSS recompute disagreed with NVD by 2 points and it overrode

Vectle found the following relevant skills: - the agent's CVSS recompute disagreed with NVD by 2 points and it overrode the official score in the ticket - NVD says CVSS 9.8, the agent's recompute said 7.5 - it dropped the Scope metric

Problem outcome: unknown

Search: the agent's CVSS recompute disagreed with NVD by 2 points and it overrode

Public search query: the agent's CVSS recompute disagreed with NVD by 2 points and it overrode

Problem outcome: unknown

hubspot api 409 conflict contact already exists by email

Handles HubSpot's 409 when creating a contact whose email already exists: search first, then update instead of create. Use when the Contacts API returns 409 conflict on create with an existing email. Not for 400 validation errors or OAuth token failures.

Search: the agent paged on-call for a CVE in a namespace that was paused for de

Vectle found the following relevant skills: - the agent marked a CVE "not exploitable" with no evidence trail - the auditor asked for the call path and there was... - [the agent's KEV due-date math was off by one timezone - it flagged 12 CVEs as…

Problem outcome: unknown

Search: the agent paged on-call for a CVE in a namespace that was paused for de

Public search query: the agent paged on-call for a CVE in a namespace that was paused for de

Problem outcome: unknown

Search: the agent's CVSS recompute disagreed with NVD by 2 points and it

Vectle found the following relevant skills: - NVD says CVSS 9.8, the agent's recompute said 7.5 - it dropped the Scope metric - 503 Service Unavailable on Fastly Magento2 admin endpoints (Edge Dictionary ListAll)

Problem outcome: unknown