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/dlupiak/claude-session-dashboard/fix-issuenpx skills add dlupiak/claude-session-dashboard --skill fix-issuegit 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/fix-issue)<a href="https://agentmods.dev/skills/dlupiak/claude-session-dashboard/fix-issue"><img src="https://agentmods.dev/badge/skills/dlupiak/claude-session-dashboard/fix-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.00012 | $0.00307 |
| Opus 5 | $0.00006 | $0.00153 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
fix-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 4d 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
Fix GitHub Issue Workflow
You are fixing GitHub issue #$ARGUMENTS.number.
Steps
1. Understand
- Fetch issue details:
gh issue view $ARGUMENTS.number - Read related code and understand the root cause
- If the issue is unclear, ask the user for clarification
2. Branch
- Create a fix branch:
feature/fix-$ARGUMENTS.number git checkout -b feature/fix-$ARGUMENTS.number
3. Fix
- If the root cause is unclear, use superpowers:systematic-debugging before writing any fix
- Implement the minimal fix
- Add or update tests to cover the bug
- Run typecheck + lint after changes
4. Verify
- Use superpowers:verification-before-completion — run commands and read actual output before claiming fixed
- Run the full quality suite:
cd apps/web npm run typecheck npm run lint npm run test - All must pass
5. PR
- Commit with message:
fix: <description> (closes #$ARGUMENTS.number) - Push and create PR:
gh pr create - Link the issue in the PR body
- Report the PR URL
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.
- 4d ago First seen · 45 lines · 12 tokens per session scan A c02917e631eb
fix-issue is a skill published in the GitHub repository dlupiak/claude-session-dashboard (67 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 307 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-09-01.
Other skills, from other repositories
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
omh-failure-signal-audit
This is a Hermes-native failure-signal-audit workflow skill.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
thinking-five-whys-plus
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
thinking-map-territory
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
e2e-test-create
Analyze React component source code to understand UI structure, then generate idiomatic Cypress E2E tests following Metabase conventions. Falls back to Playwright MCP browser exploration only when code reading and screenshot debugging are insufficient.