Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Check if findings are triggerable in production v1.0.0

Use this resource to check whether security findings still trigger in production release builds

New

  • 413 downloads
  • 209 likes
  • 186 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install production-viability-finding-filter

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent checks validated findings against the production configuration: release builds with assertions disabled, debug-only features. It keeps those still reachable and drops the rest. You get a filtered list with the reasoning for each decision.

Mostly picked by

Updated November 2, 2026

Card for the “Check if findings are triggerable in production” skill

Details

Generates with
Your agent's model
Licence
Apache-2.0

Similar resources

View all

What you get

  • SKILL.md: role, command, input-output contract and steps
  • SKILL.md: target locator resolution rules

Good fit for

  • Findings are validated and you need to know if production is affected
  • A finding only triggers with assertions enabled

Not for

    Tags

    • security
    • production
    • findings
    • triage

    About

    You say

    “Filter this review's findings to keep only those that trigger in a production build.”

    Card for the “Check if findings are triggerable in production” skill

    Skill published by google under the Apache-2.0 license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to check whether security findings still trigger in production release builds
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE11.3 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • SKILL.md18 KB

    Origin and licence

    Listed unmodified

    Author
    google
    Source
    github.com/google/mantis/tree/f3162c039ecd9c9d5d8bc404dd1373c7ca3152f7/skills/mantis-critic
    Licence
    Apache-2.0

    Notice

    « mantis-critic » (google, Apache-2.0) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.