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/dryvist/claude-code-plugins/session-statusnpx skills add dryvist/claude-code-plugins --skill session-statusgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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.00102 | $0.03070 |
| Opus 5 | $0.00051 | $0.01535 |
| Sonnet 5 | $0.00020 | $0.00614 |
| Haiku 4.5 | $0.00010 | $0.00307 |
Grade A, and why
session-status 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session and Repository Status Analysis
This skill provides a read-only snapshot of the current session's progress, remaining work, encountered issues, and repository state. It does not perform any repository cleanup (like deleting branches or worktrees) or wrap up the session.
State warning: Branch state, remote tracking, TaskList contents, and plan checklist state all change between invocations. Re-run every git/gh command and re-call
TaskListfrom Step 1; never trust prior outputs from this conversation.
Two modes
| Invocation | Mode | Use |
|---|---|---|
/session-status (default) |
Full — Steps 1–5, the dashboard + next-session prompt | end of session, wrap-up, deciding what to hand off |
/session-status mid |
Mid-session — the quick check below | mid-flight "where am I: what's done, what's left" |
Both modes re-derive live state; neither performs cleanup. Mid-session mode is a fast orientation snapshot — it skips the conversation-history scan (Step 2), the triage (Step 4), and the next-session prompt (Step 5). Reach for it when you just want to see progress, not plan a handoff.
Mid-session mode
Do only this, then stop:
-
Resolve the plan file (Step 1a) and read its open checklist items with line numbers. Call
TaskList. -
If — and only if — the cwd is a repository, run
git status -sband note branch and ahead/behind:git rev-parse --is-inside-work-tree >/dev/null 2>&1When that fails, omit the
Branch:line entirely. Do not print an error and do not print a placeholder. -
Count done vs remaining across both the plan checklist and
TaskList. -
Print the compact snapshot — plain language, no dashboard:
Mid-session: <n> done / <m> left
Just finished: <most recent completed item, in human terms>
Now / next: <the in_progress item, or the next open one>
Still open: <short list of remaining items, plan line #s or task IDs>
Branch: <name> (<ahead/behind/clean>) ← omit if not a repository
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 · 303 lines · 102 tokens per session scan A 6b6b8b1ed3a2
session-status is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 102 tokens to every session and 3,070 once invoked, about $0.0005 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
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…