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 strikersam/autonomous-ai-agency --skill release-readinessgit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/release-readiness)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/release-readiness"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/release-readiness/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/strikersam/autonomous-ai-agency/release-readiness"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/release-readiness.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.00029 | $0.00690 |
| Opus 5 | $0.00015 | $0.00345 |
| Sonnet 5 | $0.00006 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
release-readiness 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: release-readiness
When to Use
Before any version tag or deployment to a production/shared instance.
Instructions
Work through this checklist in order. Do not proceed to the next step if any item fails.
1 — Tests green
pytest -v
All tests must pass. Zero failures, zero errors.
2 — Changelog updated
grep -n "Unreleased" docs/changelog.md
There must be at least one entry under ## [Unreleased].
If the section says _(nothing pending)_, the changelog has NOT been updated — stop here.
3 — Determine the version bump
Using Semantic Versioning:
MAJOR— breaking API or behaviour change (existing clients must change)MINOR— new feature, backwards-compatiblePATCH— bug fix, backwards-compatible
Check docs/changelog.md for the current version to determine the next version.
4 — Update changelog
In docs/changelog.md:
- Change
## [Unreleased]to## [X.Y.Z] — YYYY-MM-DD - Add a new empty
## [Unreleased]section at the top with_(nothing pending)_
5 — Commit the changelog update
git add docs/changelog.md
git commit -m "chore: release vX.Y.Z"
6 — Tag the release
git tag vX.Y.Z
git push origin vX.Y.Z
7 — Verify CI on the tag
Check that the CI workflow passes on the tagged commit.
See .github/workflows/ci.yml.
8 — Post-release
- Update
.env.exampleif any new environment variables were introduced. - Update
README.mdif setup instructions changed. - Notify via Telegram bot if the server is running:
python telegram_bot.py(if configured).
Acceptance Checks
-
pytest -vexits 0 -
docs/changelog.md[Unreleased]section had entries - Changelog moved to versioned section with date
-
git tag vX.Y.Zcreated - CI passes on the tag
-
.env.exampleupdated if needed -
README.mdupdated if needed
Rollback Plan
If a release is found to be broken after tagging:
- Delete the tag:
git tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Z - Revert the release commit:
git revert HEAD - Fix the issue in a new commit
- Re-run this release-readiness checklist
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.
- 12d ago First seen · 101 lines · 29 tokens per session scan A 02060e1e3438
release-readiness is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 690 once invoked, about $0.0001 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-31.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
changelog-scan
Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.