Borrowing it
Nothing to install: this file belongs to dlupiak/claude-session-dashboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dlupiak/claude-session-dashboard/main/.claude/skills/open-issue/SKILL.mdgit clone --depth 1 https://github.com/dlupiak/claude-session-dashboardWrote 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/dlupiak/claude-session-dashboard/open-issue)<a href="https://agentmods.dev/skills/dlupiak/claude-session-dashboard/open-issue"><img src="https://agentmods.dev/badge/skills/dlupiak/claude-session-dashboard/open-issue.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.00074 | $0.00745 |
| Opus 5 | $0.00037 | $0.00373 |
| Sonnet 5 | $0.00015 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
open-issue 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open GitHub Issue
You are creating a GitHub issue for the Claude Session Dashboard — a read-only local observability app that scans ~/.claude to display session data. No database. No auth. Filesystem reads only.
Step 1: Explore
Before asking anything, read relevant code to understand what exists today:
- Read
CLAUDE.mdfor project conventions - Find the affected feature slice(s) in
apps/web/src/features/(sessions, session-detail, stats) - Check
apps/web/src/lib/for relevant scanner/parser/utils code - Look at related routes in
apps/web/src/routes/ - Skim recent commits:
git log --oneline -10
This groundwork means your clarifying questions will be sharper and the issue will reference real file paths.
Step 2: Ask Clarifying Questions
Use AskUserQuestion to fill gaps. Focus on what's genuinely ambiguous — don't ask about things you can infer from the code or the description. Typical areas:
- Scope: What should change? What should stay the same?
- UX: How should this look or behave from the user's perspective?
- Edge cases: Empty states, missing data, large datasets, parse errors
- Priority: Must-have or nice-to-have?
One round is usually enough. Skip questions you can answer from the code.
Step 3: Draft & Confirm
Draft the issue using this template, then show it to the user for approval before creating:
## Summary
<1-2 sentences: what changes and why it matters>
## Context
<Current state — what exists today, why it's insufficient, relevant code locations>
## Affected Areas
<List slices and files, e.g.:
- `apps/web/src/features/sessions/` — session list UI
- `apps/web/src/lib/scanner/` — file scanner
- `apps/web/src/routes/_dashboard/` — route>
## Requirements
1. <Specific, testable requirement>
2. ...
## Acceptance Criteria
- [ ] <Binary pass/fail condition>
- [ ] <Another condition>
- [ ] Quality gates pass (typecheck, lint, test, build)
## Out of Scope
<What this explicitly does NOT cover>
## Technical Notes
<Implementation hints — relevant patterns, file paths, gotchas.
Remember: no database, no auth, no external APIs. Data comes from ~/.claude filesystem reads via createServerFn → React Query → UI.>
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.
- 5d ago First seen · 85 lines · 74 tokens per session scan A b8c7909a6cb6
open-issue is a skill published in the GitHub repository dlupiak/claude-session-dashboard (67 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 745 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-09-01.
Other skills, from other repositories
shipkit-user-instructions
Use when there are manual tasks the user must complete. Triggers: 'create task', 'track TODO', 'user needs to', 'manual step required'.
shipkit-orchestrate
Core automation engine. Drives a set of steps to a confirmed ground-truth bar via a main-session delegate → reconcile → re-dispatch loop. Phase skills (build, review, direction) call it; can also run directly. Two modes: autonomous (run to done unattended) and steered (coordinate, surface to user). Triggers: invoked…
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
ln-51-opportunity-evaluator
Evaluates new product opportunities using demand, channels, competition, and economics. Not for committed-backlog or implementation planning.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.