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/smart-ai-memory/attune-ai/releasenpx skills add Smart-AI-Memory/attune-ai --skill releasegit clone --depth 1 https://github.com/Smart-AI-Memory/attune-aiWrote 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/smart-ai-memory/attune-ai/release)<a href="https://agentmods.dev/skills/smart-ai-memory/attune-ai/release"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/release.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.00006 | $0.00813 |
| Opus 5 | $0.00003 | $0.00407 |
| Sonnet 5 | $0.00001 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release
Release preparation, validation, and publishing.
Routes
| Subcommand | Action |
|---|---|
prep |
Release readiness checks |
security |
Pre-release security audit |
health |
Code health check |
audit |
Release-audit stage — what class of defect could this release introduce? |
publish |
Version bump and publish |
Usage
/release # Ask what to do
/release prep # Release prep checks
/release security # Security audit
/release health # Health check
/release audit # Release-audit stage (packet + sitting)
/release publish # Publish release
Behavior
prep
Run release preparation workflow:
uv run attune workflow run release-prep
This checks:
- Test suite passes
- No critical security issues
- Documentation is current
- Changelog is updated
security
Run security audit focused on release readiness:
uv run attune workflow run security-audit --path src/
health
Run code health checks:
- Test coverage
- Lint status
- Type check status
- Dependency audit
audit
The release-audit stage (docs/specs/release-audit-stage/). The other
release surfaces check hygiene; this one asks what class of defect THIS
diff could have introduced. It sits every release (D2) — an empty
residual still sits, which is cheap by design.
python -m attune.classes.stage --repo <owner/name>
Six steps: baseline (merge-base vs the last release tag) -> reconcile
(CLOSED gates green in CI, bound to this head SHA) -> sweep (rules over
the changed src/ surface, D10) -> residual packet -> sitting (three
seats, one round) -> chair rules.
Exit codes are the contract:
| Code | Meaning | What to do |
|---|---|---|
| 0 | Ready for the chair | Rule each residual item |
| 1 | Aborted | Read aborted_at — a red reconcile means fix CI first; seats never sit on a broken baseline |
| 2 | Residual exceeds schema v1 | Split the release. The chair splits; the tool re-runs each partition. Never truncate. |
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.
- 5d ago First seen · 126 lines · 6 tokens per session scan A 13ac759dd837
release is a skill published in the GitHub repository Smart-AI-Memory/attune-ai (10 stars, last pushed today), licensed Apache-2.0. It adds 6 tokens to every session and 813 once invoked, about $0.0000 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
uncommonroute-release
Use when publishing UncommonRoute. A release is only complete after all required steps are done: version sync, validation, GitHub push/tag/release, PyPI publish, and npm publish.
release-prep
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
massgen-release-documenter
Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.
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…
release-preview
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.
release
Run the local Agent Safehouse release flow: inspect commits since the last published release, propose the next SemVer version and changelog, present a dry-run for confirmation, then update changelog, publish the GitHub release, and publish the stable Homebrew tap when confirmed.