credit-guard

From README

Credit guard Trigger Use whenever enrichment may spend credits, before bulk jobs, or when the user asks about cost/ . Rules Free first: checkcreditbalance, previewcost, getaccountanalytics. Narrow job searches with searchjobs filters and a small limit rather than broad pulls. Prefer composites (accountintel, enrichcontact, finddecisionmakers) over long primitive chains. Do not repeat the same lookup for identical inputs in one session. More than 5 rows → a sheet run (sheets skill) or a bulk job (bulk-enrichment skill). Never loop single-record tools per row. Empty/not-found results are usually free — say so when reporting. Don't ask before single-record lookups or a sheet run of 5 credits or less (e.g. filling a few new rows) — they run directly. Bulk jobs, bigger sheet runs, imports, outbound pushes and deletes answer first with needsconfirmation, a summary and a confirmationtoken — nothing has run.