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 chipi/agentic-ai-homelab --skill obs-bootgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/obs-boot)<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/obs-boot"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/obs-boot/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/chipi/agentic-ai-homelab/obs-boot"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/obs-boot.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.00080 | $0.00328 |
| Opus 5 | $0.00040 | $0.00164 |
| Sonnet 5 | $0.00016 | $0.00066 |
| Haiku 4.5 | $0.00008 | $0.00033 |
Grade A, and why
obs-boot 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 8d 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
obs-boot
Drive and verify the observability stack boot. Source runbook:
docs/recipes/observability-boot.md. Verify steps are read-only; the compose
up is shared-state and gated.
Steps
- Creds (read-only). Confirm the three Grafana Cloud values are in
infra/observability/.env(cp .env.example .envif missing). Never commit the real.env. - Config check (read-only). Run
compose-checkoninfra/observability(docker compose config -q). - Boot — SHARED-STATE, approval. From
infra/observability/in place:docker compose up -d. - Verify (read-only). In Grafana Cloud Explore, confirm node / DCGM / vLLM /
cAdvisor metrics arrive (filter
instance="homelab-1"); healthchecks green. - Dashboards + pin tags. Import the four dashboards; after a verified boot,
pin the
:latestimage tags to the concrete versions.
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.
- 8d ago First seen · 25 lines · 80 tokens per session scan A b7df53beb49a
obs-boot is a skill published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 328 once invoked, about $0.0004 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
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
mcore-run-on-slurm
How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDADEVICEMAXCONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".