Is mrr-floor-check safe to install?

SaferSkills independently audited mrr-floor-check (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/mrr-floor-check/SKILL.md · 1 file

skills/mrr-floor-check/SKILL.md1.5 KB · Markdown

name: mrr-floor-check

owner_agent: hermes

description: Daily Stripe MRR query against a configured floor. Writes snapshot JSON to data/finance/mrr_history/, fires Telegram high-priority alert on floor breach. Floor is 0 by default (silent) until Cooper tunes it after 30 days of data.

trigger: launchd com.dai.mrr-floor.plist daily at 11:00 CDT (09:00 PT) or manual via bash run.sh

mrr-floor-check

Daily MRR-vs-floor watcher. Pulls Stripe active subscriptions, sums monthly + annualized MRR, compares against data/finance/mrr_floor.yaml, snapshots to history, alerts Cooper if breached.

See SOUL.md for the floor-tuning protocol (Phase 1/2/3) and failure modes.

Manual run

bash ~/.hermes/skills/mrr-floor-check/run.sh

Output: data/finance/mrr_history/<YYYY-MM-DD>.json plus stdout STATUS=... line.

Required env / config

~/.hermes/config.yaml must contain STRIPE_SECRET_KEY: (already set since cont-7)
data/finance/mrr_floor.yaml must exist (created in this ship; default floor_usd: 0)

Outputs

data/finance/mrr_history/<YYYY-MM-DD>.json — daily snapshot:

  {
    "date": "2026-05-01",
    "current_mrr_usd": 0.00,
    "floor_usd": 0,
    "alert_threshold_pct": 90,
    "alert_triggered": false,
    "subscription_count": 0,
    "subscriptions": []
  }

Telegram message via tools/notify/telegram_send.py --priority high ONLY when alert triggered.

Status codes

STATUS=ok current_mrr=$X floor=$Y / STATUS=alert ... / STATUS=error reason=...

mrr-floor-check— agent skill

Is mrr-floor-check safe to install?

mrr-floor-check

Manual run

Required env / config

Outputs

Status codes

Audit the pieces. Scan the whole. Decide.