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/different-ai/agent-bank/publish-clinpx skills add different-ai/agent-bank --skill publish-cligit clone --depth 1 https://github.com/different-ai/agent-bankWrote 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/different-ai/agent-bank/publish-cli)<a href="https://agentmods.dev/skills/different-ai/agent-bank/publish-cli"><img src="https://agentmods.dev/badge/skills/different-ai/agent-bank/publish-cli.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.00000 | $0.00248 |
| Opus 5 | $0.00000 | $0.00124 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
publish-cli 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
publish-cli
What I Do
Publish the 0 Finance CLI (agent-bank) to npm and keep the CLI version in sync.
Prerequisites
- npm account with publish rights for
agent-bank packages/clibuilds successfully
Workflow
- Bump
packages/cli/package.jsonversion. - Update
packages/cli/src/index.ts.version()to match. - Build:
pnpm --filter ./packages/cli build. - Publish from
packages/cli:npm publish --tag latest. - Verify:
npm view agent-bank version. - Sanity check install:
bun add -g agent-bank@latestthenfinance --version.
Optional Script
packages/cli/package.jsonincludespublish:clifor step 3–4.
Common Issues
- Version prints old number:
.version()not updated insrc/index.ts. - npm rejects publish: bump package.json version.
- bun shows older version: clear cache or reinstall globally.
Completion Criteria
npm view agent-bank versionshows the new version.finance --versionmatches the published version.
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 · 35 lines · 0 tokens per session scan A 63df69eadcd0
publish-cli is a skill published in the GitHub repository different-ai/agent-bank (250 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 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-30.
Other skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.