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 agentmods add skills/microsoft/agent-framework/agent-framework-py-releasenpx skills add microsoft/agent-framework --skill agent-framework-py-releasegit clone --depth 1 https://github.com/microsoft/agent-frameworkWhat 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 | $0.00103 | $0.05426 |
| Opus 5 | $0.00051 | $0.02713 |
| Sonnet 5 | $0.00021 | $0.01085 |
| Haiku 4.5 | $0.00010 | $0.00543 |
Grade A, and why
agent-framework-py-release 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Framework Python Release
Cuts a Python release PR for the microsoft/agent-framework monorepo.
Core principle: CHANGELOG drives bumps
No more universal lockstep. A package only bumps if it has a CHANGELOG entry this cycle. Draft the CHANGELOG first, then derive the bump list from it.
Exceptions to selective bumping (these stay coupled regardless of per-package changes):
- Root
agent-frameworkis coupled toagent-framework-coreviaagent-framework-core[all]==X.Y.Z(exact pin inpython/pyproject.toml). Ifcorebumps, root bumps. Root may also bump independently for its own changes (docs/metadata/extras). - Beta-tier cohort bumps are still allowed when the user explicitly wants a fresh date stamp across all betas for cohort signaling — but this is a deliberate user decision per release, not a default.
If the user explicitly states which packages to bump (or hands over a PR list per package), treat that as authoritative.
Lifecycle tiers and version rules
Use python/.github/skills/python-package-management/SKILL.md as the source of truth for lifecycle
version patterns, date-stamp cutoffs, classifier alignment, and internal dependency updates.
For release work, derive the live tier map at release time from python/PACKAGE_STATUS.md and the actual
version = lines in each pyproject.toml. Do not hardcode counts — packages move between tiers.
Inputs to confirm before bumping
- The changeset: explicit commits/PRs the release covers, OR derive from
git log ${LAST_RELEASED_TAG}..${RELEASE_BASE} -- python/. - Per-package CHANGELOG entries: which packages will get a line in the new release section. This list IS the bump list.
- Per-released-package semver bump: for each released-tier package that has a CHANGELOG entry, decide PATCH / MINOR / MAJOR.
- Date stamp (only if any alpha/beta is being bumped): default from the
python-package-managementdate-stamp rule. - Optional cohort bump?: ask if betas should all get a new date stamp regardless of per-package changes. Default: no.
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 First seen · 393 lines · 103 tokens per session scan A 8608b4d3f100
agent-framework-py-release is a skill published in the GitHub repository microsoft/agent-framework (13,222 stars, last pushed 2d ago), licensed MIT. It adds 103 tokens to every session and 5,426 once invoked, about $0.0005 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
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
agent-collaboration
Use this skill when coordinating multiple AI agents. Covers multi-agent patterns, handoffs, and orchestration strategies.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.