agentmods.dev

memex: Skill for Claude Code

.agents/skills/memex-release/SKILL.md

memex-release is a skill for Claude Code from nicosuave/memex. It costs 49 tokens per session (1,059 once invoked), scanned A, original, MIT.

A release procedure for publishing a Memex software version across command-line archives, a Qt AppImage, a signed macOS app, and Homebrew. It also verifies the published results.

In plain words
What is it for?
Use it to prepare patch, minor, or major Memex releases, run the required checks, publish release assets, and verify them.
Why use it?
It removes the need to remember the required versioning, tagging, build, signing, publishing, and verification steps. It helps prevent incomplete or incorrectly labelled releases.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is nicosuave/memex's own configuration. It tells Claude Code how to work on memex itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything memex configures →

not rated 291repo +20 today A scan 49 tokens original MIT
View source ↗ nicosuave/memex
Reuse

Borrowing it

Nothing to install: this file belongs to nicosuave/memex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nicosuave/memex/main/.agents/skills/memex-release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nicosuave/memex

Made for: Claude Code.

Wrote 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.

agentmods badge for memex-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicosuave/memex/memex-release/github.svg)](https://agentmods.dev/skills/nicosuave/memex/memex-release)
Your own site
<a href="https://agentmods.dev/skills/nicosuave/memex/memex-release"><img src="https://agentmods.dev/badge/skills/nicosuave/memex/memex-release/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.

agentmods 80×15 button for memex-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/nicosuave/memex/memex-release"><img src="https://agentmods.dev/badge/skills/nicosuave/memex/memex-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,059 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01059
Opus 5.5 $0.00020 $0.00424
Sonnet 5.5 $0.00010 $0.00212
Haiku 4.5 $0.00005 $0.00106

Measured 3d ago against content hash 5fdc92269e1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memex-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 3d 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.

.agents/skills/memex-release/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memex release

A full release is: version bump and tag via cargo release, the tag-triggered GitHub release workflow, the locally signed macOS app plus its Homebrew cask, then verification. The repo owns the mechanics; when this file disagrees with them, trust release.toml, .github/workflows/release.yml, scripts/release_macos_local.sh, and apps/macos/scripts/publish-cask.sh.

Before starting

  • Release from the maintainer's main checkout on main, not from a worktree: cargo release refuses a detached HEAD.
  • Preserve unrelated working-tree changes; the macOS script requires a clean tree.
  • Pick the bump from the commits since the latest tag (git log --oneline $(git describe --tags --abbrev=0)..origin/main): fixes only -> patch, new user-visible capability -> minor, breaking change -> major. A requested bump does not override contrary evidence; say which you chose and why.
  • CI on the latest main commit must be green. If it is still running, wait for that exact commit.

Procedure

  1. Sync: git fetch origin --prune --tags && git pull --ff-only.
  2. Check: cargo fmt --check, mbx clippy -- -D warnings, and mbx test once. If the full suite stalls or a known timing-sensitive test fails, rerun that test alone and report the full suite as unverified rather than passed.
  3. Bump and tag: cargo release <bump> --execute --no-confirm. This updates Cargo.toml, Cargo.lock, and herdr-plugin.toml, commits "Release memex version X.Y.Z", tags vX.Y.Z, and pushes both. It does not publish to crates.io. Run it once without --execute first if unsure.
  4. Release workflow (release.yml, triggered by the tag): builds memex-X.Y.Z-macos-arm64.tar.gz and memex-X.Y.Z-linux-{x86_64,arm64}.tar.gz (each with .sha256) plus the Qt AppImage, and creates the GitHub release. Watch it with gh run list --workflow release.yml and one bounded wait.
  5. macOS app, after the GitHub release exists (needs the maintainer's local Developer ID and notarization setup): CODESIGN_IDENTITY='<Developer ID Application identity>' scripts/release_macos_local.sh X.Y.Z (NOTARY_PROFILE has a default in the script). It builds, signs, notarizes, staples, uploads memex-app-X.Y.Z-macos-arm64.zip, and updates Casks/memex-app.rb in nicosuave/homebrew-tap. Run it in the background; it takes minutes. On an upload or cask failure, retry with --publish-only X.Y.Z.
  6. Homebrew formula: memex lives in homebrew-core (the tap's tap_migrations.json points there). Nothing to push; verify with gh api repos/Homebrew/homebrew-core/contents/Formula/m/memex.rb --jq .content | base64 --decode. It usually lags the tag; report it as pending rather than failed.

Read the full file on GitHub · 72 lines

Changes

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.

  1. 3d ago First seen · 72 lines · 49 tokens per session scan A 5fdc92269e1e

Subscribe to this mod's changes

memex-release is a skill published in the GitHub repository nicosuave/memex (291 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,059 once invoked, about $0.0002 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-10-25.

Claude CodeDevOps and cloudGit and workflowRAG and vectorsReleasesbm25codex-clihybrid-searchtantivy
Related

Other skills, from other repositories

starcat-update-changelog

Update Starcat changelog documents in supports/starcat-pro/ by reading ALL git commits from the main Starcat project and generating categorized release notes in both English and Chinese. Use this skill whenever the user wants to update changelog, release notes, update records, or sync the changelog with recent…

starcat-app/Starcat · 98 tokens

multi-repo-release

Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.

Azure/GPT-RAG · 56 tokens

starcat-release-readiness

A release-readiness workflow for preparing and auditing a macOS app for the Mac App Store and direct distribution. It covers checks across branches, database changes, tests, builds, signing, notarisation, release notes, and human approval.

starcat-app/Starcat · 113 tokens

git-workflow

A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.

huangwb8/skills · 47 tokens

git-publish-release

A release assistant for GitHub, a service for hosting software projects. It compares project history and creates a GitHub Release with notes for a chosen version tag.

huangwb8/skills · 42 tokens

versioning-by-impact

Use when completing a task and deciding whether repository changes require a semantic version bump and changelog entry before commit/push.

rexleimo/aios · 29 tokens