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 commands/smart-ai-memory/empathy-framework/releasegit clone --depth 1 https://github.com/Smart-AI-Memory/empathy-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.00011 | $0.01168 |
| Opus 5 | $0.00005 | $0.00584 |
| Sonnet 5 | $0.00002 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
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 2d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management
Aliases: /ship
Release operations powered by Socratic agents that ensure quality and security before shipping.
Quick Examples
/release # Interactive menu
/release prep # Prepare release with quality checks
/release audit # Deep security audit
/release publish # Publish to registry
Discovery
Question:
header: "Task"
question: "What release task do you need?"
options:
- label: "Prepare release"
description: "Version bump, changelog, pre-release checks"
- label: "Security audit"
description: "Deep vulnerability scan with attack scenarios"
- label: "Publish release"
description: "Publish to package registry"
Prepare Release
Agent: quality-validator | Workflow: release_prep
Prepare a release with comprehensive quality validation.
Invoke:
/release prep # Interactive version selection
/release prep patch # Bump patch version (1.0.0 → 1.0.1)
/release prep minor # Bump minor version (1.0.0 → 1.1.0)
/release prep major # Bump major version (1.0.0 → 2.0.0)
/release prep 2.0.0 # Specific version
The quality-validator agent will:
- Run all tests and verify they pass
- Check for security vulnerabilities
- Update version in pyproject.toml/package.json
- Generate changelog from commits
- Verify documentation is current
- Create pre-release checklist
Pre-release checklist:
- All tests passing
- No security vulnerabilities
- Changelog updated
- Version bumped correctly
- Dependencies up to date
- Documentation current
Philosophy: Instead of just running checks, you'll hear "Tests pass, but I notice coverage dropped 5% since last release. Should we add tests before shipping?"
Security Audit
Agent: security-reviewer | Workflow: security_audit
Deep security audit with attack scenario analysis.
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.
- 2d ago First seen · 195 lines · 11 tokens per session scan A 0864badf5b18
release is a command published in the GitHub repository Smart-AI-Memory/empathy-framework (13 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,168 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-30.
Other commands, from other repositories
publish
Publish a new version of the package to npm and create a GitHub release.
Release Version
自动更新版本号、基于git日志生成修订日志、安装依赖、构建、打标签并发布到npm.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
test
Smart test runner with filtering, coverage, and health monitoring.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
framework-builder
Run the real Limitless framework builder for a topic.