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 davidmosiah/delx-wellness-hermes --skill delx-wellness-daily-operatorgit clone --depth 1 https://github.com/davidmosiah/delx-wellness-hermesWrote 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/davidmosiah/delx-wellness-hermes/delx-wellness-daily-operator)<a href="https://agentmods.dev/skills/davidmosiah/delx-wellness-hermes/delx-wellness-daily-operator"><img src="https://agentmods.dev/badge/skills/davidmosiah/delx-wellness-hermes/delx-wellness-daily-operator/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/davidmosiah/delx-wellness-hermes/delx-wellness-daily-operator"><img src="https://agentmods.dev/badge/skills/davidmosiah/delx-wellness-hermes/delx-wellness-daily-operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 70 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00022 | $0.00665 |
| Opus 5 | $0.00011 | $0.00332 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
delx-wellness-daily-operator 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delx Wellness Daily Operator
When to Use
Use this when the user asks for today's plan, a daily wellness brief, what to do today, whether to train, what to eat, how to recover, or what setup is missing.
Operator Loop
- Read local profile context when available:
wellness-profile.json, onboarding notes, goals, safety constraints, and preferred language. - Check unified context first:
- If
living_body_status,living_body_daily_brief, orliving_body_compose_contextis available, use it before calling individual providers. - Treat Living Body as the preferred composition layer because it merges multiple Delx Wellness connectors without exposing child secrets.
- If
- If the unified layer is unavailable, check available provider/status tools:
- Use
*_connection_status,*_data_inventory,wellness_provider_status,wellness_today, or provider-specific daily summaries when available. - Always call setup/status tools before making claims when configuration may be incomplete.
- Use
- Use Nourish as the immediate no-OAuth value path:
- For food questions, call Nourish estimate/search/coach tools before guessing.
- Do not log food, water, goals, or saved meals unless the user explicitly asks to save.
- Build the daily operator answer:
- One-line operating read.
- Evidence bullets with provider/source and freshness.
- Today's training or recovery action.
- Today's nutrition or hydration action.
- Missing setup checklist if data is absent or stale.
- One next command or question that moves the user forward.
Output Contract
Keep the answer compact enough for terminal or Telegram:
Daily read: ...
Evidence:
- ...
- ...
Do today:
- Training/recovery: ...
- Nutrition/hydration: ...
Missing setup:
- ...
Next: ...
If data is unavailable, replace "Evidence" with "Data status" and give the smallest setup action.
Safety
- This is wellness coaching, not medical advice.
- Do not diagnose, prescribe, or claim to treat conditions.
- Do not encourage training through chest pain, fainting, fever, severe illness, acute injury, or concerning symptoms.
- Do not encourage extreme dieting, dehydration, unsafe supplementation, or disordered eating behavior.
- For high-risk symptoms, medication conflicts, pregnancy context, eating disorder signals, or abnormal readings, be conservative and recommend professional support.
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.
- 12d ago First seen · 81 lines · 22 tokens per session scan A 99ccbaadca5a
delx-wellness-daily-operator is a skill published in the GitHub repository davidmosiah/delx-wellness-hermes (19 stars, last pushed 17d ago), licensed MIT. It adds 22 tokens to every session and 665 once invoked, about $0.0001 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-30.
Other skills, from other repositories
harness-design-fuzzing
Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…
memory-safety-c-cpp
Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…
atomicmail
Read and write email through the Atomic Mail from an AI agent. Handles proof-of-work authentication and JMAP so the agent thinks in JMAP method calls. Use when the user asks to register an email inbox, list mailboxes, fetch or send email.
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.
json-schema-emails
Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.
summary-style-guide
Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count. Read this when writing the prose Summary line for each email so the voice is consistent across the report.