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/britt/agent-skills/summarize-conversation-threadnpx skills add britt/agent-skills --skill summarize-conversation-threadgit clone --depth 1 https://github.com/britt/agent-skillsWrote 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/britt/agent-skills/summarize-conversation-thread)<a href="https://agentmods.dev/skills/britt/agent-skills/summarize-conversation-thread"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/summarize-conversation-thread.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.00058 | $0.00663 |
| Opus 5 | $0.00029 | $0.00331 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
summarize-conversation-thread 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Conversation Thread Skill
Read long GitHub issue or PR threads and produce concise summaries highlighting what matters.
When to Use
Activate when:
- Catching up on a lengthy discussion
- Preparing to contribute to an existing thread
- Extracting decisions from a closed issue
- Identifying action items from a discussion
When NOT to use: Skip for short threads (fewer than ~5 comments) — just read them directly.
Getting the Thread
First, obtain the full thread content:
- Issues:
gh issue view <number> --comments(requires theghCLI, authenticated) - PRs:
gh pr view <number> --comments - No gh CLI or no repo access: Ask the user to paste the thread content
Output Structure
## Summary: [Issue/PR Title]
**Status**: [Open/Closed] | **Comments**: [X] | **Last Activity**: [date]
### TL;DR
[2-3 sentence summary of the core discussion]
### Key Decisions
- **[Decision]**: [context and who decided]
### Action Items
- [ ] [Action] — @[owner]
### Open Questions
- [Unresolved question needing input]
### Next Steps
[What should happen next]
Guidelines
What to Include
- Decisions made and who made them
- Action items with clear owners
- Unresolved questions or blockers
- Changes in direction or scope
- Links to key comments
What to Skip
- Redundant "+1" or "me too" comments
- Off-topic tangents
- Superseded proposals
- Resolved sub-discussions
Handling Edge Cases
- Stale threads (>30 days inactive): Note this and flag if decisions may be outdated
- Heated discussions: Present all perspectives neutrally
- No resolution: Clearly state "No decision reached" and summarize options discussed
- Long threads (50+ comments): Break into phases if discussion evolved significantly
Example
## Summary: Add dark mode support (#142)
**Status**: Open | **Comments**: 23 | **Last Activity**: 2 days ago
### TL;DR
Team agreed to implement dark mode using CSS variables. Debate on whether to auto-detect system preference or default to light mode resolved in favor of auto-detect.
### Key Decisions
- **Use CSS variables**: Easier to maintain than separate stylesheets — @sarah
- **Auto-detect system preference**: Better UX, users can override — @mike
### Action Items
- [ ] Create color token system — @sarah
- [ ] Add toggle to settings page — @alex
### Next Steps
Sarah to submit initial PR with color variables by Friday.
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 · 105 lines · 58 tokens per session scan A 99008a455e91
summarize-conversation-thread is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 663 once invoked, about $0.0003 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…