OpenClacky is an open-source AI coding agent that uses OpenAI-compatible models to perform tasks through tools and subagents. It is intended for developers who want an agent with flexible model choice and lower token usage. The catalogue skills and agents extend its workflows and capabilities.
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 clacky-ai/openclacky --skill gem-releasegit clone --depth 1 https://github.com/clacky-ai/openclackyWrote 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/clacky-ai/openclacky/gem-release)<a href="https://agentmods.dev/skills/clacky-ai/openclacky/gem-release"><img src="https://agentmods.dev/badge/skills/clacky-ai/openclacky/gem-release/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/clacky-ai/openclacky/gem-release"><img src="https://agentmods.dev/badge/skills/clacky-ai/openclacky/gem-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Tool Misuse · line 173 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- low Supply Chain · line 173 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00076 | $0.02072 |
| Opus 5 | $0.00038 | $0.01036 |
| Sonnet 5 | $0.00015 | $0.00414 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade C, and why
gem-release scanned grade C with 2 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 10d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
Fresh install: curl -sSL https://raw.githubusercontent.com/clacky-ai/openclacky/main/scripts/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Fresh install: curl -sSL https://raw.githubusercontent.com/clacky-ai/openclacky/main/scripts/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gem Release Skill
Automates the complete openclacky gem release workflow via SKILL_DIR/scripts/release.sh.
Usage
- "Release a new version"
- "Publish a new gem version"
- "Release version 1.0.0.beta.1" (pre-release with explicit version)
/gem-release
Workflow
The release script (SKILL_DIR/scripts/release.sh) handles everything end-to-end:
- Pre-release checks (clean working directory, required tools)
- Run test suite (
bundle exec rspec) + web search smoke tests (real network — verifies Bing/DDG parsers still work against live HTML) - Bump version in
lib/clacky/version.rb - Update
Gemfile.lockviabundle install - Commit and push to origin, wait for CI
- Build gem (
gem build openclacky.gemspec) - Publish to RubyGems (
gem push) - Create git tag and push
- Create GitHub Release with .gem asset (uses CHANGELOG.md for notes)
- Upload .gem to Tencent Cloud OSS CDN
- Update
latest.txton OSS (stable only, unless--update-latest) - Rebuild and sync
scripts/to OSS - Cleanup build artifacts
Agent Instructions
1. Determine version and release type
Read current version:
grep 'VERSION =' lib/clacky/version.rb
Stable release (default): Increment patch version (e.g., 1.0.5 → 1.0.6). Confirm with user if unsure which part to bump (major/minor/patch).
Pre-release: Use the exact version the user specified (e.g., 2.0.0.beta.1). Before proceeding, warn about pre-release caveats (see section below).
2. Write CHANGELOG
This is the one step the agent handles manually — the script does not write changelog entries because it requires reviewing git history and exercising judgment.
-
Find the previous version tag:
git describe --tags --abbrev=0 -
Gather commits since last release:
git log <previous_tag>..HEAD --oneline -
Write a new section in
CHANGELOG.mdfollowing this format:## [X.Y.Z] - YYYY-MM-DD ### Added - Feature description ### Improved - Enhancement description ### Fixed - Bug fix description ### More - Minor items
What ships with it
1 file 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.
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.
- 10d ago First seen · 221 lines · 76 tokens per session scan C 2c87f805a0c4
gem-release is a skill published in the GitHub repository clacky-ai/openclacky (1,187 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,072 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, 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
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
pinned-release-checklist
Minimal guidance-only Skill used by release-pinned compatibility examples.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…