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/kcofoni/duplicati-mcp/releasegit clone --depth 1 https://github.com/kcofoni/duplicati-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/kcofoni/duplicati-mcp/release)<a href="https://agentmods.dev/commands/kcofoni/duplicati-mcp/release"><img src="https://agentmods.dev/badge/commands/kcofoni/duplicati-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.1 | $0.00000 | $0.00932 |
| Opus 5 | $0.00000 | $0.00466 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
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 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a new version of duplicati-mcp
Guide the user through a full release: bump version, build, commit, tag, and publish to GitHub, Docker Hub, PyPI, and the MCP registry.
Instructions
Step 0 — Determine the new version
If $ARGUMENTS is provided, use it directly as the new version (e.g. /release 1.1.0 or /release patch).
Otherwise, read the current version from pyproject.toml and ask the user:
- patch (bug fixes, docs):
X.Y.Z→X.Y.Z+1 - minor (new features, new tools):
X.Y.Z→X.Y+1.0 - major (breaking changes):
X.Y.Z→X+1.0.0 - or an explicit version number
If a bump type (patch/minor/major) is given rather than an explicit version, compute the new version from the current one.
Confirm the new version with the user before proceeding.
Step 1 — Ensure a clean state
Run git status. If there are uncommitted changes, ask the user whether to commit them first (with a message they provide) or to include them in the release commit.
Step 2 — Bump the version in all three files
Update the version string in:
pyproject.toml—version = "X.Y.Z"CHANGELOG.md— add a new## [vX.Y.Z] - YYYY-MM-DDsection at the top; ask the user for the changelog entriesmcp-publication/duplicati/server.json—"version"field and"identifier"field (docker.io/kcofoni/duplicati-mcp:vX.Y.Z)
Step 3 — Rebuild the package
uv build
The .tar.gz contains the README shown on PyPI — always rebuild.
Step 4 — Commit, tag and push to GitHub
git add .
git commit -m "Release vX.Y.Z — <summary>"
git tag vX.Y.Z
git push origin main --tags
Ask the user to confirm the commit message before running.
Step 5 — Publish to Docker Hub
Ask the user to confirm before running:
docker buildx build \
--platform linux/amd64,linux/arm64 \
-t kcofoni/duplicati-mcp:vX.Y.Z \
-t kcofoni/duplicati-mcp:latest \
--push \
.
Verify the push succeeded.
Step 6 — Publish to PyPI
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 · 112 lines · 0 tokens per session scan A 5c135803cd90
release is a command published in the GitHub repository kcofoni/duplicati-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 932 tokens. 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.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
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.