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 generation-timelinegit 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/generation-timeline)<a href="https://agentmods.dev/skills/bolivian-peru/os-moda/generation-timeline"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/generation-timeline/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/generation-timeline"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/generation-timeline.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.00032 | $0.00857 |
| Opus 5 | $0.00016 | $0.00428 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
generation-timeline 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 10d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generation Timeline — Time-Travel Debugging
Correlate NixOS generations + audit ledger + journal logs to debug issues across time.
"What changed?" Workflow
When a user reports "something broke":
1. Get the generation timeline
shell_exec({ command: "nixos-rebuild list-generations 2>/dev/null | tail -10" })
2. Get the audit ledger for the same period
event_log({ limit: 30 })
3. Correlate with journal errors
journal_logs({ priority: "err", since: "24 hours ago", lines: 50 })
4. Check memory for related context
memory_recall({ query: "config change rebuild generation", timeframe: "7d" })
5. Build the timeline
Present a unified view:
Timeline — Last 48 Hours:
Feb 19 09:30 Gen 48 applied (nixpkgs update: OpenSSL 3.1→3.2)
Feb 19 09:47 ERROR: app returned first 502 (17 min after gen 48)
Feb 19 09:48 WARNING: 12 more 502s in next minute
Feb 19 09:52 agentd detected service degradation (audit #134)
Feb 19 10:00 You: "something broke"
Root cause: Gen 48 updated OpenSSL, breaking TLS cipher
used by your app.
Options:
(a) Rollback to Gen 47 (reverts everything since)
(b) Pin OpenSSL 3.1 for your app only (overlay)
(c) Update app TLS config (best long-term fix)
"Explain my server" Workflow
When asked "what does this server do" or "explain the setup":
shell_exec({ command: "cat /etc/nixos/configuration.nix" })
shell_exec({ command: "nixos-rebuild list-generations | head -5" })
shell_exec({ command: "systemctl list-units --type=service --state=running --no-pager" })
Generate a plain-English overview:
Your Server — osModa (Hetzner CX22)
Services running:
- agentd (osModa system daemon) — since boot
- OpenClaw Gateway (AI agent interface) — port 18789
- SSH (key-auth only) — port 22
- nginx (reverse proxy) — ports 80, 443
Architecture:
Internet → nginx (443) → OpenClaw (18789)
SSH → direct access (22)
NixOS: Generation 50, built Feb 20
Resources: 2 CPU, 7.6GB RAM, 80GB disk (38% used)
Uptime: 12 hours
History: 50 generations over 18 days.
Key changes stored in audit ledger (134 entries).
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.
- 10d ago First seen · 117 lines · 32 tokens per session scan A ae1748163b8e
generation-timeline is a skill published in the GitHub repository bolivian-peru/os-moda (117 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 857 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
gateway-doctor
Use when diagnose and fix MCP gateway routing issues, health checks, and server connectivity problems. Use when working with gateway doctor.
devops-incident-responder
Use when actively responding to production incidents, diagnosing critical service failures, or conducting incident postmortems to implement permanent fixes and preventative measures.
analyzing-linux-elf-malware
Analyzes malicious Linux ELF (Executable and Linkable Format) binaries including botnets, cryptominers, ransomware, and rootkits targeting Linux servers, containers, and cloud infrastructure. Covers static analysis, dynamic tracing, and reverse engineering of x8664 and ARM ELF samples. Activates for requests involving…
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.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.