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.
git clone --depth 1 https://github.com/fockus/skill-memory-bankWrote 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/commands/fockus/skill-memory-bank/changelog)<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/changelog"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/changelog/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/commands/fockus/skill-memory-bank/changelog"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/changelog.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00179 |
| Opus 5.5 | $0.00012 | $0.00072 |
| Sonnet 5.5 | $0.00006 | $0.00036 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
changelog 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 17d 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
- Detect the latest tag:
git describe --tags --abbrev=0 2>/dev/null || echo "start" - Collect commits since the latest tag:
git log <tag>..HEAD --pretty=format:"%h %s" --no-merges - Group them by type:
feat,fix,refactor,test,docs,chore - Generate a
CHANGELOGentry in Keep a Changelog format - If
$ARGUMENTSis provided, use it as the version; otherwise propose one using semver
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.
- 17d ago Changed · +25 tokens per session 1f04ae879249
- 1mo ago First seen · 11 lines · 6 tokens per session scan A 300ee9cf8863
changelog is a command published in the GitHub repository fockus/skill-memory-bank (30 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 179 once invoked, about $0.0001 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 commands, from other repositories
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release
Create a new release with version bump, changelog update, git tag, npm publish, and optional GitHub Release.