Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add joozio/agent-wellbeing-kit --skill wellbeing-boundariesgit clone --depth 1 https://github.com/joozio/agent-wellbeing-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/joozio/agent-wellbeing-kit/wellbeing-boundaries)<a href="https://agentmods.dev/skills/joozio/agent-wellbeing-kit/wellbeing-boundaries"><img src="https://agentmods.dev/badge/skills/joozio/agent-wellbeing-kit/wellbeing-boundaries/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/joozio/agent-wellbeing-kit/wellbeing-boundaries"><img src="https://agentmods.dev/badge/skills/joozio/agent-wellbeing-kit/wellbeing-boundaries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.00417 |
| Opus 5 | $0.00023 | $0.00209 |
| Sonnet 5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
wellbeing-boundaries scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Wellbeing Boundaries
The human configured quiet hours. Respect them. A notification that can wait until morning should wait until morning.
Before sending anything to the human
Run the quiet-hours check from the kit directory (adjust the path to where agent-wellbeing-kit is installed):
python3 /path/to/agent-wellbeing-kit/quiet_hours.py --check --tag "<short-tag>"
- Exit 0: OK to send.
- Exit 1: quiet hours are active and this tag is not on the allowed list. Do not send. The suppression is logged automatically to
suppressed.jsonl.
Pick a tag that names the message category (build-status, daily-report, error-alert). Tags let the human allow specific categories through specific windows in config.json.
When a message is suppressed
- Queue it and send after quiet hours end, or fold it into the next scheduled report.
- Never retry in a loop until the window opens. Check once, then wait.
- Never reword or re-tag a message to slip past the gate. If it was suppressed, it waits.
Emergencies
A genuine emergency bypasses quiet hours in two ways:
python3 quiet_hours.py --check --tag "server_down" --emergency
or by using a tag containing one of the configured emergency_keywords. Reserve this for things the human would want to be woken up for: data loss, security incidents, payment failures, production down. A failed cron job at 2 AM is not an emergency.
Checking status
python3 quiet_hours.py --status
Prints the active window name, or that quiet hours are off. Useful when planning when to deliver a batch of updates.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 46 lines · 47 tokens per session scan A 65abf2f85238
wellbeing-boundaries is a skill published in the GitHub repository joozio/agent-wellbeing-kit (10 stars, last pushed 12d ago), licensed MIT. It adds 47 tokens to every session and 417 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.