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 encoreshao/encore-skills --skill summarize-issuegit clone --depth 1 https://github.com/encoreshao/encore-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/encoreshao/encore-skills/summarize-issue)<a href="https://agentmods.dev/skills/encoreshao/encore-skills/summarize-issue"><img src="https://agentmods.dev/badge/skills/encoreshao/encore-skills/summarize-issue/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/encoreshao/encore-skills/summarize-issue"><img src="https://agentmods.dev/badge/skills/encoreshao/encore-skills/summarize-issue.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00880 |
| Opus 5.5 | $0.00014 | $0.00352 |
| Sonnet 5.5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
summarize-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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Issue
Use when the user asks to summarize completed work and post it to the issue — e.g. "summarize this and post it to the issue", "add a summary comment to #42". Typically comes right after create-mr, once the issue is fixed and the MR exists (open or merged).
This is not the one-line "Fixed in !123" note create-mr already posts. This is a fuller, high-level recap for anyone landing on the issue later — reporter, reviewer, or future-you — who wants to know what happened without reading the diff or the whole comment thread.
Gather context
Don't summarize from memory alone — pull the actual issue, MR, and commits so the summary reflects what shipped, not what was planned.
GITLAB="$HOME/.claude/skills/gitlab-config/scripts/gitlab_api.py"
python $GITLAB sync-issue <project> <issue_iid> # issue body + existing notes
python $GITLAB get-mr <project> <mr_iid> # MR title, description, state
git log origin/<base>..<branch> --oneline # commits that make up the fix
If the MR is already merged, note that. If it's still open, say so instead of implying it's done.
Pick the shape based on outcome
This skill assumes the issue is actually fixed — use the template below for that case. If the attempt didn't fully land (still failing, blocked on something outside your control, or you couldn't verify it), don't force it into "What's done" — that misleads a reader into thinking it shipped. Replace ## Changes/## Verified with a plain ## Problem (or ## Blocked on) section stating what was tried, what actually failed or is blocking, and what's needed to unblock it. Same markdown/bullet discipline either way — headers and bullets per fact, never a run-on paragraph — just don't dress up a failure as a success.
Write the summary
High-level only — this is a recap, not a diff. No file-by-file listings, no line-count stats. Markdown, always:
## Summary
<2-3 sentences: what was wrong and what changed, in plain language.>
## Root cause
<1-2 sentences — only if non-obvious. Skip this section if the fix was straightforward.>
## Changes
- <what changed, one bullet per logical change — not per file>
- <...>
## Verified
- <what confirms this is actually fixed — test added, manually reproduced and checked, etc.>
## MR
!<mr-number> — <merged / open, awaiting review>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +4 lines 40cb893ad3aa
- 1mo ago Changed 4bbf77a234f7
- 1mo ago First seen · 73 lines · 35 tokens per session scan A 6314366b153a
summarize-issue is a skill published in the GitHub repository encoreshao/encore-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 880 once invoked, about $0.0001 per session on Opus 5.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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.
awesome-git-history-rebuild
Erases a repository's history and rebuilds it as a curated commit series over the same tree, with a backup, confirmation gates and a tree-hash proof. Use when asked to rewrite history as readable commits.
awesome-git-author-rewrite
Rewrites the author and committer on commits with a wrong identity, then force-pushes after access checks, a mirror backup and a confirmation gate. Use when a commit has the wrong name or email.
awesome-git-commit-plan
Plans a codebase as a bisectable series of commits that each build and test alone, delivered as one plan file. Use when asked to split a project into commits.