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 jxoesneon/Ciel --skill plugin-release-opsgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/plugin-release-ops)<a href="https://agentmods.dev/skills/jxoesneon/ciel/plugin-release-ops"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/plugin-release-ops.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.00043 | $0.00850 |
| Opus 5 | $0.00022 | $0.00425 |
| Sonnet 5 | $0.00009 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
plugin-release-ops 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 3d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIEL ADAPTATION: Plugin Release Ops
This skill orchestrates the full release cycle for Claude Code plugin marketplace packages. It targets marketplace.json and plugin.json — the plugin-specific manifest files — NOT generic repository releases (see opensource-and-repo-ops for that). Ciel's risk classifier gates public releases as critical, triggering user escalation before any push or publish action.
Preparation
- Analyze: Classify the change as PATCH (bug fixes), MINOR (features), or MAJOR (breaking).
- Environment: Extract repository owner and name from
git remote -v. - Paths: Verify
package.json,.claude-plugin/marketplace.json, andplugin/.claude-plugin/plugin.jsonall exist. - Release notes: Draft detailed release notes BEFORE starting the version bump.
Workflow
- Bump versions: Increment version strings in all three config files simultaneously.
- Verify consistency:
grepthe new version across all files to confirm they match. - Build: Run
npm run buildto generate fresh artifacts. - Commit:
git add -A && git commit -m "chore: bump version to X.Y.Z"— include build artifacts. - Tag:
git tag -a vX.Y.Z -m "Version X.Y.Z". - Push:
git push origin main && git push origin vX.Y.Z. - Release:
gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES". - Changelog: Regenerate
CHANGELOG.mdviagh api repos/{owner}/{repo}/releases --paginate | ./scripts/generate_changelog.js > CHANGELOG.md. - Sync: Commit and push the updated
CHANGELOG.md. - Finalize: Run
git status— the working tree MUST be clean.
Risk Classification
- Public release = critical: Git push, GitHub release creation, and npm publish are irreversible public actions.
- Ciel's autonomy ladder escalates all critical operations to the user before execution.
- Never auto-approve a push or release without explicit user confirmation.
Checklist
- All config files have matching versions
npm run buildsucceeded- Git tag created and pushed
- GitHub release created with notes
CHANGELOG.mdupdated and pushedgit statusshows clean tree
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.
- 3d ago First seen · 64 lines · 43 tokens per session scan A 11c08eb29938
plugin-release-ops is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 43 tokens to every session and 850 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
delivery
Fecha o ciclo de entrega local — build check, bump semântico, changelog e commit convencional. Deploy remoto somente sob a condição dupla do Ops. Use para "finalizar tarefa", "fazer release" ou "publicar versão".
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
git-mirror-audit
Verify configured secondary git mirrors are present and not drifting from the primary remote/default branch.