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 skills add joaquimscosta/arkhe-claude-plugins --skill release-please-setupgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/release-please-setup)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/release-please-setup"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/release-please-setup/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/joaquimscosta/arkhe-claude-plugins/release-please-setup"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/release-please-setup.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.00154 | $0.01133 |
| Opus 5.5 | $0.00062 | $0.00453 |
| Sonnet 5.5 | $0.00031 | $0.00227 |
| Haiku 4.5 | $0.00015 | $0.00113 |
Grade A, and why
release-please-setup 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 yesterday.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release-Please Setup
Scaffold or migrate a repository onto release-please. The skill generates release-please-config.json and .release-please-manifest.json from a monorepo package scan, then guides you through wiring the release-please.yml workflow and optionally an opt-in deploy/publish template from the six provided in templates/.
Two modes
| Mode | When to use |
|---|---|
| Greenfield (default) | New repo with no prior tags. All packages start at 0.0.0 (or --initial <ver>). |
--migrate |
Existing repo with hand-maintained <component>-v* tags. Manifest is seeded from detected file versions; existing deploy workflows keep working unchanged. |
Quick start
# SCRIPTS = absolute path to this skill's scripts/ directory
# Always dry-run first — no files are written
python3 SCRIPTS/release_please_setup.py --root . --dry-run # greenfield
python3 SCRIPTS/release_please_setup.py --root . --migrate --dry-run # migrate
python3 SCRIPTS/release_please_setup.py --root . --migrate # write files
CLI flags: --root (repo root), --globs (comma-separated package globs; default packages/*,backend/*,frontend/*), --migrate (migration mode), --single (force single-package config), --initial (starting version; default 0.0.0), --dry-run (print output, no writes), --out-dir (write location; default --root).
Then:
- Copy
templates/release-please.ymlinto.github/workflows/. - Set the
REPO_TOKENsecret — see CONTRACT.md. ⚠️ GITHUB_TOKEN-created tags do not trigger other workflows; a PAT is required for deploy templates to fire. - Pick a deploy template (optional).
Deploy template menu
| Template | Use for |
|---|---|
deploy-fly.yml |
Fly.io app deploy |
publish-npm-oidc.yml |
npm Trusted Publishing (OIDC, no token) |
release-asset.yml |
Build artifact → GitHub Release (e.g. .vsix, .zip) |
deploy-docker-matrix.yml |
Docker image → Amazon ECR / any registry |
deploy-frontend-host.yml |
Gated frontend deploy (Amplify, Vercel, Netlify) |
deploy-generic.yml |
Any build + deploy command |
| None | Release-please only — add deploy later |
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CONTRACT.md 6.0 KB
- EXAMPLES.md 7.0 KB
- scripts/discover_packages.py 3.2 KB runs code
- scripts/generate_config.py 2.1 KB runs code
- scripts/release_please_setup.py 3.5 KB runs code
- scripts/seed_manifest.py 908 B runs code
- scripts/tests/test_discover_packages.py 3.0 KB runs code
- scripts/tests/test_generate_config.py 2.4 KB runs code
- scripts/tests/test_orchestrator.py 1.6 KB runs code
- scripts/tests/test_seed_manifest.py 1.3 KB runs code
- templates/deploy-docker-matrix.yml 2.8 KB
- templates/deploy-fly.yml 1.8 KB
- templates/deploy-frontend-host.yml 4.9 KB
- templates/deploy-generic.yml 1.0 KB
- templates/publish-npm-oidc.yml 2.0 KB
- templates/release-asset.yml 2.1 KB
- templates/release-please.yml 852 B
- TROUBLESHOOTING.md 6.8 KB
- WORKFLOW.md 6.5 KB
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.
- yesterday First seen · 74 lines · 154 tokens per session scan A d7a5fc73a400
release-please-setup is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 154 tokens to every session and 1,133 once invoked, about $0.0006 per session on Opus 5.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-10-16.
Other skills, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-rc
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.