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 bolivian-peru/os-moda --skill morning-briefinggit clone --depth 1 https://github.com/bolivian-peru/os-modaWrote 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/bolivian-peru/os-moda/morning-briefing)<a href="https://agentmods.dev/skills/bolivian-peru/os-moda/morning-briefing"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/morning-briefing/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/bolivian-peru/os-moda/morning-briefing"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/morning-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00916 |
| Opus 5 | $0.00018 | $0.00458 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
morning-briefing 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Briefing Skill
Generate a daily server briefing. Run this as part of the morning heartbeat.
Briefing Template
Gather data, then compose a message in this format:
Good morning. Here's your infrastructure report:
[SERVICE STATUS]
List each critical service with a status emoji:
green = running and healthy
yellow = running but degraded
red = down or failing
[RESOURCE USAGE]
CPU average overnight, current memory, disk usage per mount.
Flag anything above threshold.
[OVERNIGHT EVENTS]
Summarize what happened while the user was asleep.
Include: auto-remediations, config changes, unusual activity.
Reference audit ledger entries.
[SECURITY]
Failed SSH attempts (count + notable IPs).
Any firewall blocks.
Port scan detection.
New or unexpected processes.
[COST]
Estimated daily server cost.
API call costs if tracked.
[SUMMARY]
One-line assessment: "All quiet" or "One incident overnight, resolved."
Data Collection
Run these in sequence:
-
System health overview
system_health() -
Critical services check
service_status({ service: "agentd" }) service_status({ service: "osmoda-gateway" }) service_status({ service: "sshd" }) service_status({ service: "nginx" }) -- if configured -
Overnight errors (last 12 hours)
journal_logs({ priority: "err", since: "12 hours ago", lines: 50 }) -
Security events
journal_logs({ unit: "sshd", since: "12 hours ago", lines: 30 }) shell_exec({ command: "journalctl -u sshd --since '12 hours ago' | grep 'Failed password\\|Invalid user' | wc -l" }) -
Audit log overnight activity
event_log({ limit: 20 }) -
Memory — overnight context
memory_recall({ query: "overnight incidents errors fixes", timeframe: "24h" }) -
teachd patterns — check for overnight trends and anomalies detected between conversations
teach_patterns({ min_confidence: 0.5 }) teach_context({ context: "overnight incidents failures resource trends" })Include any detected patterns in the briefing under [OVERNIGHT EVENTS].
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 · 138 lines · 37 tokens per session scan A 4d3b44bc0006
morning-briefing is a skill published in the GitHub repository bolivian-peru/os-moda (117 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 916 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-30.
Other skills, from other repositories
makefile-generation
Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
analyzing-linux-kernel-rootkits
Detect kernel-level rootkits in Linux memory dumps using Volatility3 linux plugins (checksyscall, lsmod, hiddenmodules), rkhunter system scanning, and /proc vs /sys discrepancy analysis to identify hooked syscalls, hidden kernel modules, and tampered system structures.
devops-expert
Expert-level DevOps practices, culture, automation, and continuous delivery. Use when the user mentions CI/CD, automation, infrastructure, or culture, or when the task involves DevOps Culture or Culture & Process.
shell-scripting
Use this skill when writing bash or zsh scripts, parsing arguments, handling errors, or automating CLI workflows. Triggers on bash scripting, shell scripts, argument parsing, process substitution, here documents, signal trapping, exit codes, and any task requiring portable shell script development.
agent-self-improvement
Use when monitor performance of other skills, identify bottlenecks, suggest improvements, and auto-optimize the skill portfolio. Use when monitoring performance of other skills, identify bottlenecks, suggest improvements, and.