HEARTBEAT.mddevelopmentOpenclawv1.0.1

GitHub Actions Cost Tracker

Compares GitHub Actions run activity with billed usage across your repos. Flags spikes for review.

Setup time: ~5 min
Model: Haiku
Cost: Depends on schedule Calculate your exact cost at Clawback
Last updated: Oct 18, 2026
byRunbooks Communitycontributor

Template

HEARTBEAT.md
On a configured daily Automation (not installed by this template):
1. For each tracked repo, fetch workflow runs for the reporting window:
   gh api -X GET --paginate repos/{owner}/{repo}/actions/runs -f created=YYYY-MM-DD..YYYY-MM-DD --jq '.workflow_runs[] | {id, name, status, conclusion, run_started_at, updated_at}'
2. Summarize run counts, failed runs, reruns, and workflows worth investigating. A run's wall-clock timestamps do not establish billed job minutes or runner charges.
3. If you have authorized billing access and a supported billing source, compare the same reporting window with GitHub's Actions usage in the account or organization billing view. Otherwise request a manual review of that view. Note the repository owner, plan allowance, runner type, and any reporting delay. If access is missing, report spend as unknown, not zero.
4. Daily report: workflow activity and exceptions, billing usage when available, source and time window for each number, and mismatches that need a human review. Do not call an estimated workflow duration a bill.
5. Alert only on a documented threshold in the billing source or an explicitly labeled run-activity anomaly. Include a link to the run and billing view; confirm delivery.
6. Weekly: compare GitHub billing usage with run-activity trends and investigate discrepancies. Do not claim per-workflow spend without a supported cost allocation source.

Setup

  1. 1

    Copy the HEARTBEAT.md content below into your OpenClaw workspace at `~/.openclaw/workspace/HEARTBEAT.md`.

  2. 2

    Install the required skills: `clawhub install github`, `clawhub install message`.

  3. 3

    Open your agent channel (Telegram or any connected channel) and send a message to confirm it's running.

  4. 4

    Your agent will follow the schedule in HEARTBEAT.md automatically. Check back in 30 minutes to see it in action.

  5. 5

    Customize the template: adjust timing, thresholds, and notification targets to fit your setup.

Tip: The template uses placeholder values like {your brand} or {repo}. Replace these with your actual values before saving.

Install commands

Save the template to your OpenClaw workspace, then install the required skills.

# 1. Save the template
cp <download> ~/.openclaw/workspace/HEARTBEAT.md

# 2. Install skills
clawhub install github
clawhub install message

Version History

v1.0.1Use GitHub billing evidence instead of elapsed workflow time for cost claimsOct 18, 2026
v1.0.0Initial releaseMar 16, 2026

Framework

Openclaw

Skills required

github →message →

Estimated cost

Depends on schedule

on Haiku model

Calculate your exact cost at Clawback

File type

HEARTBEAT.md

Defines scheduled tasks. Runs on a heartbeat interval.

Version

v1.0.1

Updated Oct 18, 2026

Contributor

Runbooks Community →

Community submission

Spending too much?

Track and optimize your agent API costs.

Try Clawback →

You might also like

HEARTBEAT.md

GitHub PR Reviewer

Auto-review new PRs during business hours. Post summaries, flag issues.

~$0.50/day · ~5 min setup

HEARTBEAT.md

CI Monitor

Watch GitHub Actions. Alert on failures with the relevant logs.

~$0.20/day · ~3 min setup

HEARTBEAT.md

Deploy Tracker

Track deployments across repos. Daily changelog of what shipped.

~$0.15/day · ~5 min setup

← Back to all runbooks