Add coffee-paladin

[pawelkwaczynski]

coffee-paladin is a thermal guard for Apple Silicon Macs. When the chip gets too hot it pauses the heavy job with SIGSTOP and resumes it once the machine cools, so long work survives the heat instead of being killed by it. It also gates Claude Code, Codex CLI and Gemini CLI before heavy commands, and keeps the readings from before a hard shutdown for a repair report.

Repository: https://github.com/pawelkwaczynski/coffee-paladin
License: MIT. macOS 14+, Apple Silicon. No sudo, no kernel extension, no root daemon.

Added under Development & Workflow in alphabetical order. Opened at the maintainers' invitation in pawelkwaczynski/coffee-paladin#1.

[github-actions]

✅ Contribution check passed. @pawelkwaczynski, catalog validation succeeded.

scan passed

All 1 source-repository scanner job(s) passed. Catalog validation passed.

Recommended: add scanner CI for security

This listing can merge without it. HOL still scans pawelkwaczynski/coffee-paladin independently.

We recommend including hashgraph-online/ai-plugin-scanner-action under .github/workflows/ on push and pull_request. Continuous scanning keeps this catalog safer for MCP servers, skills, plugins, and other agent extensions people install from HOL.

Adding it:

• protects the ecosystem by catching secrets, dangerous hooks, and supply-chain issues before they ship;
• keeps the listing at the full trust score (without maintainer CI it stays eligible, with a 10% trust-score reduction);
• can surface findings in GitHub code scanning.

See CONTRIBUTING.md and SCANNER_GUIDE.md.

View the latest sweep.

[pawelkwaczynski]

Small note for whoever picks this up: the project shipped 3.3.3 this morning, and the README first screen was rewritten a moment ago to lead with what the tool does for coding agents (a hook that makes the agent ask before heavy work on a hot Mac, a statusline carrying chip temperature into the session, and per-session core usage in the menu bar). The repository URL and the one-line description in this PR are unchanged and stay accurate.

[github-actions]

🎉 Hey @pawelkwaczynski, your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

• Owner-verified badge on your plugin's registry listing
• Trust score visibility and analytics for your plugin
• Direct claim link to share with your community
• Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

1. Visit hol.org/guard/plugins
2. Find your plugin and click "Verify ownership"
3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.

[kantorcodes]

Hi @pawelkwaczynski — a quick follow-up about your plugin pawelkwaczynski/coffee-paladin.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verifying ownership takes about 30 seconds and unlocks the owner-verified badge, plugin analytics, and the author dashboard. Sign in with GitHub; no repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.

[kantorcodes]

Hi @pawelkwaczynski — a quick follow-up about your plugin pawelkwaczynski/coffee-paladin.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.

[kantorcodes]

Hi @pawelkwaczynski — a quick follow-up about your plugin pawelkwaczynski/coffee-paladin.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.