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 agentmods add skills/nomadop/session-watcher/sw-explainnpx skills add nomadop/session-watcher --skill sw-explaingit clone --depth 1 https://github.com/nomadop/session-watcherWhat 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 | $0.00054 | $0.00395 |
| Opus 5 | $0.00027 | $0.00198 |
| Sonnet 5 | $0.00011 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
sw-explain 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 2d 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
Explain a Session Watcher metric
When the user asks about a metric:
- Call
watcher_statusto confirm the dashboard is running and get its URL (metric VALUES live on the dashboard the user can see — do not expect raw numbers from MCP). - Explain the requested metric in plain language.
- Contextualize against the flat-valley / AM-GM bound where relevant.
Metric glossary
- br (bill regret) — how much extra you pay vs optimal restart timing, as a fraction. 0.10 = amber, 0.25 = red.
br = mf × pp. - mf (movable fraction) — the share of cost that timing can affect. Capped at √2−1 ≈ 41.4% by AM-GM — even worst-case timing can't cost more than that.
- pp — the timing-penalty shape term
(u−1)²/(2u); minimized at u=1 (the sweet spot). - u — normalized position
(x−1)/dhat. u<1 = left arm (cost still falling, no action). u=1 = sweet. u>1 = past sweet. - wall — where continuing costs more per turn than a full restart.
- sweet / valley —
xSweet = 1 + dhat, the cost-curve minimum; the valley around it is flat (small timing penalty).
Frame reassuringly: e.g. "br=18% sounds high, but the ceiling is ~41.4%, so you're inside the flat valley — no urgency."
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.
- 2d ago First seen · 24 lines · 54 tokens per session scan A 7feba52421aa
sw-explain is a skill published in the GitHub repository nomadop/session-watcher (3 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 395 once invoked, about $0.0003 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
dvalin-security-scan
Scan code for injection, hardcoded secrets, XSS, dynamic code execution, and unsafe shell use. Use after writing or modifying code that handles user input, builds queries or commands, touches authentication, or adds a dependency — and whenever the user asks for a security check, audit, or review. Runs locally with no…
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
c-03-repo-bootstrap
Bootstrap onboarding for undocumented repos or existing memory slices. Builds root overviews, route-local overview pillars, evidence packs, file cards, onboarding waves, deleted-slice cleanup, curator reviews, and handoff while keeping the orchestrator thin.
c-12-closeout
Close out approved Agents Remember edits by preserving approval authority, mandatory strict code quality before code commit, missing-onboarding checks, external-memory refresh, memory quality, ledger alignment, and no automatic push.
l-01-agent-lifecycles
The agent lifecycles: one lifecycle per agent type, under one roof. Routes every session by exactly three conditions (spawn-role env -> fresh role brief -> otherwise free-chat launcher), carries the minimal lifecycle frame (the six lifecycle signals every session shares), and houses the self-contained per-role…
c-09-git-worktree-manager
Create, attach to, report on, integrate, finalize, and clean up Agents Remember worktree-backed tasks while preserving delegated/human approval gates and external-memory compatibility.