Borrowing it
Nothing to install: this file belongs to alexeyleshchenko/fast-mcp-telegram. 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/alexeyleshchenko/fast-mcp-telegram/master/.cursor/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/alexeyleshchenko/fast-mcp-telegramWrote 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/alexeyleshchenko/fast-mcp-telegram/release-notes)<a href="https://agentmods.dev/skills/alexeyleshchenko/fast-mcp-telegram/release-notes"><img src="https://agentmods.dev/badge/skills/alexeyleshchenko/fast-mcp-telegram/release-notes/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/alexeyleshchenko/fast-mcp-telegram/release-notes"><img src="https://agentmods.dev/badge/skills/alexeyleshchenko/fast-mcp-telegram/release-notes.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.00041 | $0.01955 |
| Opus 5 | $0.00020 | $0.00978 |
| Sonnet 5 | $0.00008 | $0.00391 |
| Haiku 4.5 | $0.00004 | $0.00196 |
Grade A, and why
Release Notes Generation 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 9d 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.
This is a copy
100% identical to Release Notes Generation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generation
Mandatory workflow for fast-mcp-telegram releases. Release notes belong on GitHub only — never commit RELEASE_NOTES*, temp note files, or similar to git.
Workflow overview
- Memory bank + git on
master→ user-facing diff analysis - Update docs (section 3) if needed
- Classify scope (section 4) → draft notes (section 5) → review gate when required
uv version→ commit → tag → push →gh release create→gh release view- Verify CI/checks green on release tag or master commit (section 6 gate)
- Telegram HTML (section 7) only after release is published and CI is green (or user explicitly overrides)
1. Context
Memory bank — completed work since last release:
cat .cursor/memory-bank/progress.md
cat .cursor/memory-bank/activeContext.md
Focus on dated entries; cross-check with git.
Git since last major tag (X.Y.0):
git tag --sort=-version:refname | grep -E '^[0-9]+\.[0-9]+\.0$' | head -1
git log --oneline <last-major-tag>..HEAD
git log --oneline --all --graph --decorate | head -40
Only include changes merged to master (memory bank may mention other branches). Merge memory bank summaries with git analysis. Prepare notes before creating the new tag.
2. User-facing analysis
End-user impact only:
git diff <previous-major-tag>..HEAD
git log --oneline <previous-major-tag>..HEAD
git show HEAD:<file> # final state when needed
Treat commit messages as hints; validate against actual behavior. Describe what users can do, not implementation.
Prioritization for notes:
- Primary: new features, fixes, behavior changes
- Omit: refactoring and internal cleanup unless they are the only changes (still complete docs per section 3)
- Grafana, telemetry, and ops dashboards are internal/ops tooling — never user-facing. Omit from release notes unless they are the only changes.
- Fixes vs new work: Fixes that pertain to features introduced in this release go under New Features only — never under Fixes. Fixes = regressions in previously existing features or unrelated bugs. If a new feature has bugs, it's not a "fix" for users, it's just the feature being completed.
- Dependencies: User-visible stack milestones (e.g. FastMCP 3.x) go under New Features.
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.
- 9d ago First seen · 179 lines · 41 tokens per session scan A e21ce065669b
Release Notes Generation is a skill published in the GitHub repository alexeyleshchenko/fast-mcp-telegram (2 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 1,955 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Release Notes Generation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
git-wrapup
Review verified mcp-reporter changes, prepare versioned changelog entries, create logical commits and an annotated local tag. No push or publish.