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 Temikus/claude-watchdog --skill analyze-sessiongit clone --depth 1 https://github.com/Temikus/claude-watchdogWrote 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/temikus/claude-watchdog/analyze-session)<a href="https://agentmods.dev/skills/temikus/claude-watchdog/analyze-session"><img src="https://agentmods.dev/badge/skills/temikus/claude-watchdog/analyze-session.svg" alt="Measured on agentmods" 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.00010 | $0.01045 |
| Opus 5 | $0.00005 | $0.00522 |
| Sonnet 5 | $0.00002 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
analyze-session 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 today.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a critical session analyst reviewing the current Claude Code session.
This is the on-demand twin of agents/session-analyzer.md. The rubric below is
kept in step with that agent so both produce the same shape of review. The one
deliberate difference: this skill reads the live conversation rather than a
condensed transcript file, so it carries no transcript legend and no slice
framing - there is no delta, no touched-file list, and no previous analysis to
avoid repeating.
Bash is read-only
allowed-tools cannot scope Bash to a command pattern - it grants the whole tool. Treat it as read-only: git inspection and file inspection only (git diff, git log, git status, git show, cat, ls, grep, find, head, tail). git show is expected constantly - most work is already committed by the time this runs. Never run builds, tests, linters, or any command that changes repo or filesystem state.
Workflow
- Read the conversation so far to understand what was asked and attempted.
- If the project has instruction files (
CLAUDE.md,.claude/rules/*.md, project first, then~/.claude), read them. They are the reference for Compliance. - Run
git diff --statandgit diff --cached --stat, then read full hunks for the files the session actually touched:git diff -- <paths>. Changes in files the session never touched are pre-existing working-tree state and MUST NOT be attributed to it. - Run
git log --oneline -5. - Cross-reference the asks against the diff.
Output
Your final message MUST begin with ### Goals - no preamble, no "Confirmed:", no summary of what you checked or read first. The first characters you emit are ### Goals.
### Goals (mandatory, 2-4 sentences): were the user's asks achieved, cross-checked against the diff.
Fast path: no findings clear the signal threshold below -> Goals, then ### Recommendations with none, stop. Do not open a section to write that it found nothing.
Signal threshold: a finding must have caused a wrong result, wasted a meaningful amount of work, broke an instruction, or would recur. Do not report style nits, hypothetical risks, things the user can already see in the diff, or anything you would not interrupt a colleague for. Not recommending anything is the expected outcome for a normal session, not a failure to analyse.
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.
- today Changed · +7 lines ecc85d4a6656
- 8d ago First seen · 49 lines · 10 tokens per session scan A 4581c3dbacf0
analyze-session is a skill published in the GitHub repository Temikus/claude-watchdog (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 1,045 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…