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.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.00063 | $0.01431 |
| Opus 5 | $0.00032 | $0.00715 |
| Sonnet 5 | $0.00013 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
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 yesterday.
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 — 115 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 sub-bullets. No semicolon joining two facts. Two wrapped lines is the ceiling.
- 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. Read the released sections first. If they carry an emoji and a bold label, or past tense, match them — a changelog that switches voice mid-file reads worse than one in the wrong voice. Length and jargon are not style: those rules hold everywhere.
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, not a tour of every facet. 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.
- yesterday Changed · +49 lines · +10 tokens per session 4d346c4a8a3c
- 6d 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 (17 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 63 tokens to every session and 1,431 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-30.
Other skills, from other repositories
taiyi-integration
TaiyiForge 第9阶段 — 闭环归档，CHANGELOG.md。四端通用。.
changelog-gen
Changelog 生成器 - 从 Git 历史自动生成 CHANGELOG.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
git-mirror-audit
Verify configured secondary git mirrors are present and not drifting from the primary remote/default branch.