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 skills add ArabelaTso/Skills-4-SE --skill bug-history-summarizergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/bug-history-summarizer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/bug-history-summarizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/bug-history-summarizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/bug-history-summarizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/bug-history-summarizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00106 | $0.01753 |
| Opus 5 | $0.00053 | $0.00877 |
| Sonnet 5 | $0.00021 | $0.00351 |
| Haiku 4.5 | $0.00011 | $0.00175 |
Grade A, and why
bug-history-summarizer 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 12d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug History Summarizer
Trace and summarize the complete lifecycle of a bug across code versions.
Workflow
Follow these steps to generate a comprehensive bug history summary:
1. Identify the Bug and Gather Context
Collect essential information:
- Bug identifier: Issue number, commit hash, or bug description
- Repository: Target codebase with version history
- Version range: Specific versions/commits to analyze (or entire history)
- Related artifacts: Issue reports, pull requests, commit messages, test results
2. Trace Bug Introduction
Identify when and how the bug was introduced:
Using git blame and bisect:
- Run
git blameon affected files to find when problematic lines were added - Use
git bisectto pinpoint the exact commit that introduced the bug - Analyze the introducing commit: author, date, purpose, related changes
Analyze introduction context:
- What was the original intent of the change?
- Was it a new feature, refactoring, or bug fix?
- Were there code review comments or warnings?
- What tests existed at the time?
3. Track Detection History
Document when and how the bug was discovered:
- Initial detection: When was the bug first reported or noticed?
- Detection method: User report, automated test, code review, production incident?
- Time to detection: How long between introduction and discovery?
- Severity assessment: How was the bug initially classified?
4. Analyze Fix Attempts
Chronicle all attempts to fix the bug:
For each fix attempt:
- Commit hash and date
- Author and reviewer
- Fix approach and code changes
- Test coverage added
- Whether the fix was successful or reverted
Identify patterns:
- Multiple fix attempts indicate complexity
- Reverted fixes suggest incomplete understanding
- Test additions show learning from the bug
5. Check for Regressions
Identify if the bug reappeared after being fixed:
- Search for related bug reports after the fix
- Check if the fix was reverted or modified
- Look for similar bugs in related code
- Analyze if the bug reoccurred in different contexts
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.
- 12d ago First seen · 238 lines · 106 tokens per session scan A 1209e1d03a61
bug-history-summarizer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 21d ago), licensed Apache-2.0. It adds 106 tokens to every session and 1,753 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-30.
Other skills, from other repositories
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
bim-consistency-checker
Check BIM model consistency: naming conventions, parameter completeness, spatial relationships, and data integrity across model elements.
022-root-cause-analysis
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when a maintainer directly asks to find the…