Borrowing it
Nothing to install: this file belongs to mbk-dev/okama-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mbk-dev/okama-mcp/main/.agents/skills/release-okama-mcp/SKILL.mdgit clone --depth 1 https://github.com/mbk-dev/okama-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/mbk-dev/okama-mcp/release-okama-mcp)<a href="https://agentmods.dev/skills/mbk-dev/okama-mcp/release-okama-mcp"><img src="https://agentmods.dev/badge/skills/mbk-dev/okama-mcp/release-okama-mcp/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/skills/mbk-dev/okama-mcp/release-okama-mcp"><img src="https://agentmods.dev/badge/skills/mbk-dev/okama-mcp/release-okama-mcp.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.00149 | $0.02872 |
| Opus 5 | $0.00075 | $0.01436 |
| Sonnet 5 | $0.00030 | $0.00574 |
| Haiku 4.5 | $0.00015 | $0.00287 |
Grade B, and why
release-okama-mcp scanned grade B with 2 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Deploy to secondvds** (dir owned by okama_mcp; passwordless sudo is set up; Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://mcp.okama.io/ | diff - deploy/nginx/index.html && echo "LANDING == REPO" How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing okama-mcp
Publishing is tag-driven: pushing a v* tag triggers two GitHub Actions
workflows — release.yml (build + publish to PyPI via Trusted Publishing)
and publish-mcp-registry.yml (wait for PyPI → GitHub OIDC → mcp-publisher publish to registry.modelcontextprotocol.io). Your job is the steps around
that automation. Do them in order.
Guardrails (read first)
- PyPI versions are immutable. A version can never be re-uploaded or reused.
Never push a
vX.Y.Ztag until every pre-flight check below is green. If a release fails after PyPI has accepted the upload, do not retry the same version — bump to the next patch and start over. - Three versions must match exactly: the tag (
X.Y.Z),pyproject.toml[tool.poetry] version,server.jsontop-levelversion, andserver.jsonpackages[0].version. Both workflows hard-fail otherwise. - The tag push is the irreversible, outward step. Treat it like a deploy: get the user's go-ahead before pushing the tag.
- Never commit
poetry.lock(it is gitignored).
1. Pre-flight
git checkout main && git pull --ff-only
git status --short # must be clean
git tag --sort=-v:refname | head -3 # see the latest released version
Pick the new version with semver, judged against changes since the last tag:
- patch (
x.y.Z) — bugfixes / docs only, no API change. - minor (
x.Y.0) — new tools or new optional params, backward compatible. - major (
X.0.0) — a breaking change to a tool/spec contract.
New okama tools or new optional parameters are minor.
Run the quality gates — all must be clean:
poetry run pytest -q
poetry run ruff check .
poetry run pytest -m integration # optional but recommended: hits api.okama.io
2. Bump the version (three places, identical value)
Set NEW=X.Y.Z, then edit to that value:
pyproject.toml→version = "X.Y.Z"server.json→ top-level"version": "X.Y.Z"server.json→packages[0].version"version": "X.Y.Z"
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.
- 10d ago First seen · 237 lines · 149 tokens per session scan B a9d1d2aa1708
release-okama-mcp is a skill published in the GitHub repository mbk-dev/okama-mcp (4 stars, last pushed 9d ago), licensed MIT. It adds 149 tokens to every session and 2,872 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.