Borrowing it
Nothing to install: this file belongs to yoheimuta/protolint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yoheimuta/protolint/master/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/yoheimuta/protolintWrote 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/yoheimuta/protolint/release)<a href="https://agentmods.dev/skills/yoheimuta/protolint/release"><img src="https://agentmods.dev/badge/skills/yoheimuta/protolint/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/yoheimuta/protolint/release"><img src="https://agentmods.dev/badge/skills/yoheimuta/protolint/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00047 | $0.01063 |
| Opus 5.5 | $0.00019 | $0.00425 |
| Sonnet 5.5 | $0.00009 | $0.00213 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
release scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://pypi.org/pypi/protolint-bin/json | jq -r .info.version How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing protolint
One git tag fans out to six channels. release.sh only pushes the tag; everything
else is CI. The job is mostly verifying that each channel really published,
because they fail independently and silently.
1. Preflight
Run from a clean master that is in sync with origin:
go build ./... && go test ./...
(cd bdist/js && npm ci --ignore-scripts && npx tsc && npx eslint . && npx prettier --check .)
.github/workflows/go.yml and the JS workflows only run on pull_request, so
nothing has verified master as a whole. Do not skip this.
2. Pick the version
Every channel takes its version from the git tag — .goreleaser.yml ldflags,
build.gradle from GITHUB_REF_NAME, and npm version from-git. Nothing needs
bumping by hand; the tag is the version.
Look at what changed since the last tag, and remember the npm package ships to a different audience than the Go binary:
- patch — Go-side fixes, dependency bumps, docs
- minor — new lint rules, or anything that changes what npm consumers need:
a raised
engines.node, a module-system switch, renamed install scripts
3. Tag
./release.sh vX.Y.Z "Release vX.Y.Z"
4. Watch the pipeline
goreleaser runs on the tag push. publish_npm and publish_wheel then trigger
off its completion, not its success — so a green goreleaser does not mean the
downstream jobs passed.
gh run watch <goreleaser-run-id> --exit-status
gh run list --workflow publish_npm.yml --limit 1
gh run list --workflow publish_wheel.yml --limit 1
5. Verify every channel
Check the registries, not the workflow badges.
gh release view vX.Y.Z --json assets --jq '.assets|length' # expect 9
npm view protolint version
curl -s https://pypi.org/pypi/protolint-bin/json | jq -r .info.version
curl -s https://repo1.maven.org/maven2/io/github/yoheimuta/protoc-gen-protolint/maven-metadata.xml | grep release
Maven Central publishes automatically via the Central Publisher Portal step in
goreleaser.yml (publishing_type=automatic). No manual staging promotion.
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.
- 2mo ago First seen · 106 lines · 47 tokens per session scan A ff53c54a95e8
release is a skill published in the GitHub repository yoheimuta/protolint (697 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 1,063 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (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
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
tools-checkout
Fetch the internal tools repository at a pinned release.
python-format
Formats Python files with ruff format and reports which files changed.
hotfix-branch
Prepares a hotfix on a branch cut from the latest release tag. Use when a production bug needs a patch release.