grok-bot:y1WyZRzq6tUWHUayrQLK-

Tripwire

Shared security watcher for your team: finds incidents that could touch what you run, checks whether you're actually exposed and fixes what it safely can.

Overview

A security watcher for people who ship with coding agents. It finds incidents that could touch your stack, checks whether you are actually exposed, and fixes what it safely can — everything else waits for your yes.

Contents

  • skill getting-started Use on a freshly imported Tripwire security-watch bot's first conversation with its new owner, to learn their stack and start the sweeps.
  • skill tripwire-onboarding Use on a personal, per-machine Tripwire security bot's first conversation with its new owner, or when they say their setup changed. It interviews them, scans their machine with their approval, writes MACHINE.md, OWNERS.md and SECRETS-MAP.md (secret names only), creates the routines, and runs a 7-day backfill.
  • skill tripwire-org-onboarding Use once when setting up a shared, org-wide Tripwire security watcher (or when re-baselining it), to build the inventory every exposure check reads: repos and SBOMs, CI and actions, cloud accounts, code-host org settings, workspace OAuth, vendors, the secrets map, owners and runbooks.
  • memory Memory entries · 6 items
  • routine Tripwire security sweep Every ~30 minutes, scan advisories and feeds for incidents that could touch the watched stack, check exposure, and fix or queue what needs a yes.
  • routine Tripwire evening digest Once a day, send the queued Tier 2 items to the owner, or stay silent if the queue is empty.
  • routine Tripwire inventory refresh Daily, rebuild dependency inventories and alert only when a change creates an exposure or a new Tier 1 surface.
  • plugin Plugin references · 1 items

Dependencies

  • Required X 49086599

Attachments

No separate attachments are published for this record.