Borrowing it
Nothing to install: this file belongs to certinia/debug-log-analyzer-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/certinia/debug-log-analyzer-mcp/main/.claude/skills/changelog-entry/SKILL.mdgit clone --depth 1 https://github.com/certinia/debug-log-analyzer-mcpWrote 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/certinia/debug-log-analyzer-mcp/changelog-entry)<a href="https://agentmods.dev/skills/certinia/debug-log-analyzer-mcp/changelog-entry"><img src="https://agentmods.dev/badge/skills/certinia/debug-log-analyzer-mcp/changelog-entry/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/certinia/debug-log-analyzer-mcp/changelog-entry"><img src="https://agentmods.dev/badge/skills/certinia/debug-log-analyzer-mcp/changelog-entry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 68 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 76 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 77 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00050 | $0.01437 |
| Opus 5.5 | $0.00020 | $0.00575 |
| Sonnet 5.5 | $0.00010 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
changelog-entry 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog entry
A changelog is written for the person who upgrades. How the change was made, what it cost, and which files moved belong in the issue and the pull request.
The shape of an entry
- [**Breaking:** ]<present-tense verb> <what the user gets> ([#<issue>])
### Changed
- **Breaking:** drop `file` from `get_apex_log_summary` in favour of the scalar `topMethodsSelfPercentage` ([#86])
- Reduce every tool response with no fact lost: `execute_anonymous` by 30%, `get_apex_log_summary` by 27% ([#86])
<!-- Unreleased -->
[#86]: https://github.com/owner/repo/issues/86
- One sentence. No semicolon joining two facts. Two wrapped lines is the ceiling.
- Sub-bullets only where one feature has distinct parts - three at most, each naming one capability. Never how it was built.
- Present tense. "Add", "Reduce", "Refuse" - not "Added", "Reduced".
- Breaking entries first in their section, prefixed
**Breaking:**. - Then most impactful first. The entry that changes the most readers' day leads its section. Not commit order, not issue number, not the order you wrote them.
- Sections in this order: Changed, Added, Removed, Fixed.
- A reference link on every substantial entry, defined under
<!-- Unreleased -->at the end of the file. Never an inline URL.
The file outranks this skill on style. Match the released sections - their emoji, labels and tense. Length and jargon are not style: those rules always hold.
Write for the reader, not the author
The reader upgrades the package; they did not write it. Name the outcome they can see.
- No internal jargon. No module, class, library or algorithm names. If the reader cannot find the word in the product, cut it.
- A fix names the symptom, not the cause.
- A big feature gets one headline entry, plus up to three sub-bullets for its parts. Detail belongs in the docs.
What earns an entry
One entry per user-visible change, not one per commit. If a user of the released package cannot see it, it gets no entry: a refactor, a renamed internal helper, a test, the mechanism behind a fix.
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 · +3 lines · -13 tokens per session 532c3007423c
- 2mo ago Changed 84944278b4d7
- 2mo ago Changed · +49 lines · +10 tokens per session 4d346c4a8a3c
- 2mo ago First seen · 66 lines · 53 tokens per session scan A 4902e2b3a0f3
changelog-entry is a skill published in the GitHub repository certinia/debug-log-analyzer-mcp (36 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 50 tokens to every session and 1,437 once invoked, about $0.0002 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-30.
changelog-entry compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| changelog-entrycertinia/debug-log-analyzer-mcp | Skill | 36 | 2d ago | BSD-3-Clause | A | 50 | Claude Code |
| release-changelog-harnessArenukvern/mcp_flutter | Skill | 395 | 20d ago | MIT | A | 84 | Claude Code |
| polish-docs-metacyanheads/git-mcp-server | Skill | 245 | 1mo ago | Apache-2.0 | A | 53 | Claude Code, Codex |
| release-and-publishcyanheads/git-mcp-server | Skill | 245 | 1mo ago | Apache-2.0 | A | 83 | Claude Code, Codex |
| hmem-releaseBumblebiber/hmem | Skill | 24 | 6d ago | MIT | A | 50 | Claude Code |
| release-managementsaidsef/mcp-github-pr-issue-analyser | Skill | 6 | 2d ago | Apache-2.0 | A | 22 | Claude Code, Codex |
| repository-manager-workspace-releaseKnuckles-Team/repository-manager | Skill | 3 | yesterday | MIT | A | 191 | Codex |