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/2sem/davinci-resolve-lite-mcp/releasegit clone --depth 1 https://github.com/2sem/davinci-resolve-lite-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/commands/2sem/davinci-resolve-lite-mcp/release)<a href="https://agentmods.dev/commands/2sem/davinci-resolve-lite-mcp/release"><img src="https://agentmods.dev/badge/commands/2sem/davinci-resolve-lite-mcp/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 | $0.00028 | $0.00820 |
| Opus 5 | $0.00014 | $0.00410 |
| Sonnet 5 | $0.00006 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
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 4d 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
Run the full release flow for this repo. Follow it in order; do not skip the tag/release step at the end — that step has been missed before.
-
Determine the next version. Read
SERVER_VERSIONinsrc/resolve_mcp/config.pyfor the current version. Look atCHANGELOG.md's## Unreleasedsection for what shipped since the last release, and bump appropriately (new tools/features → minor; fixes only → patch). If## Unreleasedis empty, ask the user what to include before proceeding — do not invent a release with no content. -
Branch. From a clean
main, create brancha.b.c(version number only, no prefix), e.g.git checkout -b 0.18.0. -
Bump. In one commit only:
CHANGELOG.md: rename## Unreleased→## a.b.csrc/resolve_mcp/config.py:SERVER_VERSION = "a.b.c"server.json:"version": "a.b.c"- Run
python3 tests/test_server.pyto sanity-check before committing. - Commit message:
bump: release a.b.c— this must be the ONLY commit on this branch.
-
Push + PR. Push the branch and open a PR into
maintitledRelease a.b.c. The PR body must include a full patch note: the complete list of changes since the last release (pull this from the## a.b.cCHANGELOG section you just wrote, not a summary). Open the PR in browser. -
Wait for explicit merge instruction. Never merge a release PR without the user explicitly saying so (human review / simulator test gate) — this is non-negotiable regardless of how the release flow was triggered.
-
On merge instruction: merge, then tag + release — do not stop after the merge.
gh pr merge <n> --merge --delete-branchgit checkout main && git pull --ff-only- Create the tag and GitHub release together:
gh release create va.b.c --title "va.b.c — <short summary>" --notes-file <patch-note-file> --target main. Write the release notes to a scratch file first (a## Patch note (changes since X.Y.Z)section mirroring the CHANGELOG entry, plus a## Notessection citing the constituent PR(s) and test status) — match the tone/format of prior releases (gh release view v0.16.0for reference). - Confirm with
gh release view va.b.cand report the release URL back to the user. - Publishing the release triggers
.github/workflows/publish.yml, which auto-publishes to PyPI via Trusted Publishing (no token handling needed). Check it succeeded:gh run list --workflow=publish.yml --limit 1. If PyPI's trusted-publisher hasn't been configured yet (one-time manual step on pypi.org — see CONTRIBUTING.md's Release flow section), this run will fail; that does not block the GitHub release, just note it to the user. - MCP Registry: run
mcp-publisher publishfrom the repo root (needs an activemcp-publisher login githubsession — the user's GitHub identity, not something to log in as on their behalf). Registry versions are immutable, so this is required every release, not automated in CI. If not logged in, tell the user rather than attempting the OAuth device flow silently.
Do not consider the release finished until step 6's tag + release exist — a merged bump commit alone is not a release.
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.
- 4d ago First seen · 31 lines · 28 tokens per session scan A 03b455d3e9c3
release is a command published in the GitHub repository 2sem/davinci-resolve-lite-mcp (4 stars, last pushed 11d ago), licensed MIT. It adds 28 tokens to every session and 820 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-31.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
Prepare a release by updating docs and bumping the version.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.