Borrowing it
Nothing to install: this file belongs to BarryYangi/vibetime. 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/BarryYangi/vibetime/main/.agents/skills/vibetime-release/SKILL.mdgit clone --depth 1 https://github.com/BarryYangi/vibetimeWrote 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/barryyangi/vibetime/vibetime-release)<a href="https://agentmods.dev/skills/barryyangi/vibetime/vibetime-release"><img src="https://agentmods.dev/badge/skills/barryyangi/vibetime/vibetime-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/barryyangi/vibetime/vibetime-release"><img src="https://agentmods.dev/badge/skills/barryyangi/vibetime/vibetime-release.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.00088 | $0.00996 |
| Opus 5.5 | $0.00035 | $0.00398 |
| Sonnet 5.5 | $0.00018 | $0.00199 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
vibetime-release 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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeTime Release
This project releases from main with date-based versions such as 2026.5.18. Tags use v<version>, for example v2026.5.18.
Source of truth
- Workspace package versions live in:
package.jsonpackages/core/package.jsonpackages/hook/package.jsonpackages/desktop/package.json
- GitHub Actions release packaging is triggered by pushing tags matching
v*. - The CI workflow creates the GitHub Release after quality, macOS, and Windows packaging jobs pass.
Release workflow
- Inspect state first.
rtk git status -sb
rtk git tag --sort=-creatordate | head -20
gh release list --limit 10
Do not continue if the worktree has unrelated uncommitted changes. Preserve user changes.
- Determine the target version.
- If the user says a short date like
5.18, use the existing version scheme and current release year to formYYYY.5.18. - Confirm the target tag does not already exist:
rtk git tag --list 'v<version>'
gh release view 'v<version>' --json tagName,name,url 2>/dev/null || true
- Collect release-note source commits before creating the version bump commit.
rtk git log --oneline --decorate 'v<previous-version>..HEAD'
git log --format='- %s (%h)' 'v<previous-version>..HEAD'
Use the actual user-facing changes between the previous release tag and the target release. Omit pure version-bump commits from notes.
- Bump all workspace package versions.
Only update the four package manifests listed above unless the package manager actually changes the lockfile. Keep the diff limited to version fields.
- Validate the bump.
For a version-only release bump after code was already verified in the same thread:
rtk pnpm typecheck
rtk pnpm lint
If code changes have not already been verified, run the broader relevant test suite or rtk pnpm run ci before tagging.
- Commit and tag.
rtk git add package.json packages/core/package.json packages/hook/package.json packages/desktop/package.json
rtk git commit -m "Bump version to <version>"
rtk git tag 'v<version>'
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.
- 1mo ago First seen · 141 lines · 88 tokens per session scan A 24cb185eadee
vibetime-release is a skill published in the GitHub repository BarryYangi/vibetime (8 stars, last pushed 5mo ago), licensed MIT. It adds 88 tokens to every session and 996 once invoked, about $0.0004 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.
Other skills, from other repositories
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
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.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
skillshare-app-release
A release workflow for shipping the skillshare desktop application on macOS, Windows, and Linux. It coordinates the release pull request, automated builds, GitHub release, updater feed, and Homebrew package.