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/doublej/consult-user-mcp/release-appnpx skills add doublej/consult-user-mcp --skill release-appgit clone --depth 1 https://github.com/doublej/consult-user-mcpWrote 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/doublej/consult-user-mcp/release-app)<a href="https://agentmods.dev/skills/doublej/consult-user-mcp/release-app"><img src="https://agentmods.dev/badge/skills/doublej/consult-user-mcp/release-app.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 | $0.00075 | $0.01312 |
| Opus 5 | $0.00037 | $0.00656 |
| Sonnet 5 | $0.00015 | $0.00262 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
release-app 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Consult User MCP
Two platforms, two procedures. They share docs/src/lib/data/releases.json as the single source of truth.
Never run gh release create without attaching assets. A release with no assets breaks the auto-updater for everyone already on the previous version.
macOS
Runs entirely on this machine.
- Update
macos-app/VERSION. - If
macos-app/Sources/Resources/base-prompt.mdchanged, bump its version comment (first line). See.claude/rules/baseprompt.md. - Add the release entry to
docs/src/lib/data/releases.json. Write user-facing benefits, not commit messages — see.claude/rules/release-notes.md. bun run changelog— regeneratesCHANGELOG.md. Never hand-edit it.bash scripts/validate-baseprompt-version.sh.- Commit everything.
bash scripts/release.sh --platform macos— builds, packages, tags, creates the GitHub release.
--dry-run validates preconditions without executing. Use it first when anything about the state is uncertain.
Two assets, both required
A macOS release ships a .dmg and a .zip, and neither is optional:
| Asset | Consumed by |
|---|---|
Consult.User.MCP.dmg |
a human downloading from the releases page — drag to /Applications |
Consult.User.MCP.app.zip |
install.sh and the in-app updater, both of which pick the first .zip asset |
make-dmg.sh builds and signs the dmg; dropping the zip breaks the auto-updater
for everyone already installed.
The zip must contain no AppleDouble members. ditto -c -k encodes any
extended attribute as a ._name entry, and update.sh extracting that adds an
unsealed file to the bundle — the updated app then fails codesign --verify and
will not launch. build-app.sh runs xattr -cr before signing and release.sh
fails the release if any ._ entry survives. Both guards exist because one
xattr, set just by having run the app, shipped a bricked updater in 2.6.5.
bash scripts/check-changelog-sources.sh confirms the change list the update
prompt shows is actually fetchable. It needs at least one of the two sources in
AppURLs.releasesJSONSources — the Pages copy comes from the docs deploy, so it
lags a fresh release by a few minutes and the raw GitHub fallback covers the gap.
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 · 115 lines · 75 tokens per session scan A 44ff003fedc2
release-app is a skill published in the GitHub repository doublej/consult-user-mcp (40 stars, last pushed 16d ago), licensed MIT. It adds 75 tokens to every session and 1,312 once invoked, about $0.0004 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 skills, from other repositories
bump-version
Use when bumping the AionUi version: query AionCore release, verify artifacts, update package.json, generate CHANGELOG, branch, commit, push, create PR, auto-merge, tag release.
release-notes
Generate a GitHub release note draft for this Obsidian plugin repository. Use when the user asks to write, draft, or prepare release notes for a new version. Invoked with a version number argument (e.g. "0.11.0", "0.11.0-preview.1"). Analyzes git history and code diffs since the previous release to produce user-facing…
lov-release-via-cicd
Configure CI/CD and publish new versions for Node, Tauri, Vite, shell, and GitHub Release projects. Use when the user asks to setup release workflow, publish a new version, verify macOS signing/notarization, recover a failed GitHub Release, or mentions "release-via-cicd", "配置并发布新版", "签名", "notarize", "GitHub Release"…
dsh-plugin-publisher
Publish a validated DSH plugin package (@deepseek-ai/dsh- or @lovstudio/dsh-) to npm, git, or tarball channels and verify it loads in the DeepSeek Harness. Use when the user asks to publish, release, or ship a plugin. 触发：发布插件 / 上架插件 / release dsh 插件。.
lov-skill-optimizer
Audit and optimize one or more existing Agent Skills from a canonical source path, then bump semver, update README/SKILL.md/skill.yaml/CHANGELOG.md, and verify installed copies and catalog synchronization. Checks frontmatter, trigger quality, CLI hygiene, naming, portability, version drift, dirty worktrees, shared…
lov-skill-publisher
Publish or submit a validated Skill. Default to the LovStudio official website, run lov-skill-pricing automatically, and use other channels only when explicitly named.