Borrowing it
Nothing to install: this file belongs to rome-os/rome. 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/rome-os/rome/main/.claude/skills/release-rome-image/SKILL.mdgit clone --depth 1 https://github.com/rome-os/romeWrote 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/rome-os/rome/release-rome-image)<a href="https://agentmods.dev/skills/rome-os/rome/release-rome-image"><img src="https://agentmods.dev/badge/skills/rome-os/rome/release-rome-image/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/rome-os/rome/release-rome-image"><img src="https://agentmods.dev/badge/skills/rome-os/rome/release-rome-image.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 9 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00081 | $0.00905 |
| Opus 5 | $0.00041 | $0.00452 |
| Sonnet 5 | $0.00016 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
release-rome-image scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL "https://hub.docker.com/v2/repositories/yunfanye/rome/tags?page_size=20" | jq -r '.results[].name' How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a new Rome image
A pushed vX.Y.Z tag is the release. .github/workflows/docker-publish.yml builds the multi-arch image and publishes it to yunfanye/rome, with no approval gate between the push and Docker Hub. Get explicit confirmation before the push. Verify the published image after it.
The tagging contract covering the semver gate, tag immutability, and latest movement lives in docs/releases.md.
Out of scope
- Desktop releases use the
desktop-v*tag and a separate pipeline. - npm package releases belong to release-please. Never create those tags by hand.
1. Preflight
The tag lands on origin/main, and docker-publish.yml runs no CI gate of its own.
-
Read the commit that the tag will point at.
git fetch origin --tags && git rev-parse origin/main -
List the recent CI runs.
gh run list --branch main --workflow CI --limit 5 -
Find the run for the exact commit from step 1 and confirm the status is
success. CI cancels superseded runs, so a rapid series of merges leavescancelledruns on real commits. If the run failed, was cancelled, or is still running, stop and report it. -
Confirm no release is already in flight.
gh run list --workflow "Docker Hub Publish" --limit 3
2. Pick the version
-
Read the current stable tags.
git tag --list 'v[0-9]*' | sort -V | tail -5 -
For a patch release, use the helper in step 3. The helper computes the next patch version.
-
For a minor or major release, take the version from the user.
-
For a prerelease, use
vX.Y.Z-rc.N. A prerelease publishes its own docker tag and never moveslatest.
Two constraints decide the number. A published version is immutable, so re-pushing a released version fails and the fix for a bad release is the next version up. latest moves only when the new version is the highest stable version in the registry.
3. Cut the tag
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.
- 9d ago First seen · 94 lines · 81 tokens per session scan A 8d9ca240bf2a
release-rome-image is a skill published in the GitHub repository rome-os/rome (483 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 905 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
ship-feature
Ship a feature end-to-end — update tests, docs, docs-site, then release to PyPI. Use when user says "ship", "ship feature", "release", or asks to publish a new version.
release-sync
PromptHub release update skill. Use for /update-readme, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment.