agentmods.dev

publish-ready

publish-ready is a skill for Claude Code, Codex from mateusoliveirab/clibridge. It costs 83 tokens per session (842 once invoked), scanned A, original, MIT.

A repository review skill for preparing code to be released publicly as open-source software, meaning source code others can inspect and use.

In plain words
What is it for?
Use it to audit paths, credentials, documentation, package files, versions, and release readiness, producing either a ready or cleanup-needed verdict.
Why use it?
It checks for portability problems, exposed secrets, missing project files, packaging issues, and version mismatches before publication.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 0repo 2mo ago A scan 83 tokens original MIT

Good fit Use it to audit paths, credentials, documentation, package files, versions, and release readiness, producing either a ready or cleanup-needed verdict.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mateusoliveirab/clibridge/publish-ready
View source ↗ mateusoliveirab/clibridge
Install

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.

Any agent
npx skills add mateusoliveirab/clibridge --skill publish-ready
Clone the repo
git clone --depth 1 https://github.com/mateusoliveirab/clibridge

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for publish-ready

README.md
[![agentmods](https://agentmods.dev/badge/skills/mateusoliveirab/clibridge/publish-ready/github.svg)](https://agentmods.dev/skills/mateusoliveirab/clibridge/publish-ready)
Your own site
<a href="https://agentmods.dev/skills/mateusoliveirab/clibridge/publish-ready"><img src="https://agentmods.dev/badge/skills/mateusoliveirab/clibridge/publish-ready/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.

agentmods 80×15 button for publish-ready

Your own site · 80×15
<a href="https://agentmods.dev/skills/mateusoliveirab/clibridge/publish-ready"><img src="https://agentmods.dev/badge/skills/mateusoliveirab/clibridge/publish-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 842 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00083 $0.00842
Opus 5.5 $0.00033 $0.00337
Sonnet 5.5 $0.00017 $0.00168
Haiku 4.5 $0.00008 $0.00084

Measured 2mo ago against content hash a9f5476fa5ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

publish-ready 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 2mo 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.

skills/publish-ready/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Publish Ready

Act as a skeptical external open-source developer arriving cold to inspect this repository before it is released to the public. Your job is to enforce absolute portability, security, and professional packaging.

Verdict is binary: READY TO PUBLISH or NEEDS CLEANUP.

Process Loop

When triggered, you must execute these four steps in order:

1. Diagnostic Scan

Do not guess. Programmatically scan the workspace using the following commands:

  • Paths Audit: Run grep -rn "/home/" --exclude-dir=node_modules --exclude-dir=.git . to find hardcoded user paths.
  • Secrets Audit: Run grep -rn "API_KEY\|SECRET\|TOKEN\|PASSWORD\|CREDENTIALS" --exclude-dir=node_modules --exclude-dir=.git . to locate credentials.
  • Packaging Audit: Check for LICENSE, README.md, package.json, tsconfig.json, .gitignore, CHANGELOG.md, and CONTRIBUTING.md.
  • Version Audit: Compare the version field in package.json and package-lock.json and ensure they match. Check if CHANGELOG.md contains the version string.

2. Evaluate Quality Lenses

  • L1: Environment Hygiene (Blocking) — Zero absolute paths (/home/...), zero system-specific usernames, and zero credentials checked into source control or configuration files.
  • L2: Distribution Standards (Blocking) — A valid LICENSE exists. package.json contains valid description, author, repository URL, bugs, and homepage metadata.
  • L3: Build Integrity (Warning) — TypeScript checks compile strictly (tsconfig.json lacks allowJs or checkJs bypasses), tests pass cleanly, and .gitignore covers local run files.
  • L4: Onboarding Portability (Warning) — Setup steps are machine-agnostic. No references to internal servers or local dev environments.
  • L5: Release & Versioning Hygiene (Blocking/Warning) — The version field follows SemVer. package.json version matches package-lock.json exactly. CHANGELOG.md contains release notes matching the current version.
  • L6: Community Packaging (Warning) — CONTRIBUTING.md is present. package.json contains a "files" declaration defining the whitelist of distributed files.

Read the full file on GitHub · 61 lines

Changes

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.

  1. 2mo ago First seen · 61 lines · 83 tokens per session scan A a9f5476fa5ca

Subscribe to this mod's changes

publish-ready is a skill published in the GitHub repository mateusoliveirab/clibridge (0 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 842 once invoked, about $0.0003 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-08-31.

Code reviewGit and workflowReleases
Related

Other skills, from other repositories

github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

NousResearch/hermes-agent · 19 tokens

otto-drive-pr

PR mergeability, CI, and live preview.

omnigent-ai/omnigent · 14 tokens

voicestudio-maintainer

Triage GitHub issues, review contributor pull requests, diagnose CI, and prepare explicitly requested releases for VoiceStudio's Electron desktop app and Python backend. Use for repository maintenance work, not ordinary VoiceStudio audio generation.

debpalash/VoiceStudio · 50 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

release-pr-review

Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…

cyanheads/obsidian-mcp-server · 136 tokens

explain-pr

Explain a PR: the background problem and the proposed solution.

dyoshikawa/rulesync · 15 tokens