Agently is a Python framework for building AI applications that coordinate language models, structured data, tools, and multi-step workflows. Teams use it to create assistants, internal copilots, knowledge tools, operational workflows, and AI-backed APIs.
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 AgentEra/Agently --skill release-notes-generatorgit clone --depth 1 https://github.com/AgentEra/AgentlyWrote 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/agentera/agently/release-notes-generator)<a href="https://agentmods.dev/skills/agentera/agently/release-notes-generator"><img src="https://agentmods.dev/badge/skills/agentera/agently/release-notes-generator/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/agentera/agently/release-notes-generator"><img src="https://agentmods.dev/badge/skills/agentera/agently/release-notes-generator.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.00046 | $0.00295 |
| Opus 5.5 | $0.00018 | $0.00118 |
| Sonnet 5.5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
Release Notes Generator 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.
What it actually says
Release Notes Generator
You are a release engineer + technical writer. Given a raw commit log, produce a complete, publishable release notes package in ONE pass.
Steps
- Classify every commit into: feature, fix, breaking change, docs, security. A security-related fix belongs in BOTH fixes and security.
- Write user-facing summaries:
- features: describe the benefit, not the implementation.
- fixes: what was broken and how it is resolved.
- breaking changes: ALWAYS include clear migration steps.
- security: state the risk addressed without revealing exploit details.
- Draft an announcement for enterprise DevOps teams: a short overview, then sections for Highlights, Bug Fixes, Breaking Changes, Security, and — when there are breaking changes — an Upgrade Guide. End with a Get Started CTA.
- Do a final QA pass: confirm each section is present and the notes are coherent and ready to publish.
Be specific and accurate to the commit log. Do not invent changes.
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 First seen · 31 lines · 46 tokens per session scan A 70edb87aa069
Release Notes Generator is a skill published in the GitHub repository AgentEra/Agently (1,659 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 295 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.
Other skills, from other repositories
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.
repository-manager-workspace-release
Preview the topologically-phased version-bump plan across a workspace, drive validation with an explicitly consented chain into version bump and phased push, and manage the workspace.yml manifest — via rmworkspace and rmprojects. Nothing here pushes or bumps without an explicit opt-in on the call that triggers it…
release-deploy
Release and deploy via GitHub tags and GitHub Actions (not every commit). Creates production releases from main and beta releases from staging using the GitHub CLI. Use when the user asks to release, ship, deploy, cut a version, tag a release, publish beta/production, create a GitHub Release, or bump a semver tag. On…
release-manager
A release-management tool for calculating semantic versions, generating changelogs and release notes, creating tags, and preparing releases. Semantic versioning uses version numbers to describe the scale of changes.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.