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/jackfranklin/dotfiles/summarize-for-bug-reportnpx skills add jackfranklin/dotfiles --skill summarize-for-bug-reportgit clone --depth 1 https://github.com/jackfranklin/dotfilesWrote 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/jackfranklin/dotfiles/summarize-for-bug-report)<a href="https://agentmods.dev/skills/jackfranklin/dotfiles/summarize-for-bug-report"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/summarize-for-bug-report.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.00030 | $0.00371 |
| Opus 5 | $0.00015 | $0.00186 |
| Sonnet 5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
summarize-for-bug-report 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 6d 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
Bug Report
Overview
Compiles a technical exploration or conversation into a clear, minimal, and actionable bug report.
When to Use
- When a bug has been identified or explored in the conversation, and the user wants to document it as a bug report.
- When the user asks to "write a bug report" or "create a bug report from this".
Core Pattern
- Extract the core issue from the exploration or conversation history.
- Structure the bug report as follows:
- Title: A clear, concise title summarizing the bug.
- Problem Statement: What is the bug? (1-2 sentences).
- Why It Matters: The impact of the bug or why it should be fixed (1-2 sentences).
- Steps to Reproduce (if known/applicable): A clear, minimal numbered list of steps.
- Expected Behavior: What should have happened.
- Actual Behavior: What actually happened.
- Exclude any details about specific fixes, pull requests, list of affected files, code diffs, or implementation details.
- Present the bug report directly as a response in the conversation. Do not write the report to disk or save it to any file.
- Keep the report extremely focused and clear.
Common Mistakes
- Writing the bug report to a file on disk or creating an artifact.
- Including code diffs or proposed fixes in the report.
- Listing files to modify or technical details of the fix.
- Writing long paragraphs instead of punchy, scannable statements.
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.
- 6d ago First seen · 34 lines · 30 tokens per session scan A 2cd45d299da3
summarize-for-bug-report is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 371 once invoked, about $0.0002 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…