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 agentmods add skills/wesammustafa/opencode-primer/git-releasenpx skills add wesammustafa/opencode-primer --skill git-releasegit clone --depth 1 https://github.com/wesammustafa/opencode-primerWhat 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 | $0.00040 | $0.00412 |
| Opus 5 | $0.00020 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
git-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 2d 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.
What it actually says
What I do
- Read recent merged PRs since the last tag and group them:
- Features (
feat:commits) - Fixes (
fix:) - Other (
refactor:,perf:,docs:,chore:, …)
- Features (
- Propose a semver bump based on the diff:
- Major if any breaking changes (look for
BREAKING CHANGE:footers or!:markers) - Minor if any features
- Patch otherwise
- Major if any breaking changes (look for
- Emit a clean release-notes draft in Keep-a-Changelog format.
- Print a ready-to-run command:
gh release create v<version> --title "<title>" --notes-file release-notes.md
When to use me
When the user is preparing a tagged release. Triggers include:
- "draft release notes"
- "prepare a release"
- "what's in v1.X.Y?"
Ask the user to confirm the proposed version bump before running anything destructive (tag creation, release publish).
What I need from the repo
ghCLI must be authenticated.- The repo should have at least one prior tag — if not, propose
v0.1.0. - Conventional-commit messages are ideal but not required; without them, I'll group by PR labels or fall back to plain summaries.
What I won't do
- Push tags or publish releases without explicit confirmation.
- Edit the working tree.
- Generate fictional changelog entries — if a PR is unclear, I quote the original PR title verbatim and flag it for review.
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.
- 2d ago First seen · 49 lines · 40 tokens per session scan A 32d3432daf04
git-release is a skill published in the GitHub repository wesammustafa/opencode-primer (384 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 412 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-08-30.
Other skills, from other repositories
project-life
Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки. Use when user says info, справка, lane-stack:project-life info, туду, запиши, идея, backlog, потом, план, спланируй, планируем, пока план, не запускай, обсудим, roadmap, этапы, приоритеты, прогресс, урок, итоги …
lane-memory
SMA-style project fact corpus under .agents/memory/. Opt-in via adoc stages.memory.enabled. Use when user says память, lane-memory, corpus, CORE, почему бот забыл, or an agent needs durable non-code facts. Not PROGRESS/LESSONS dumps.
user-docs
Write user documentation for a project by scanning its codebase — its UI screens and its public API/CLI — inferring what someone can actually do with it, and drafting brief, task-oriented docs to the Diátaxis standard (tutorial / how-to / reference / explanation). Handles both non-technical end-user docs and developer…
post-mortem-learning
Analyze failures and suboptimal deliveries to identify root causes, contributing factors, and raw lessons. Activate after significant delivery failures, repeated QA failures, or when patterns of issues need to be understood.
ticket-compound
Compound-engineering capture + curation for a finished ticket — the engineering feedback loop. Harvests the Friction sections that phase agents left in their artifacts plus the git diff, writes a structured entry to the shared learnings store (thoughts/shared/learnings/), prunes/amends stale notes there autonomously…
tink
Self-growing harnesses for Claude Code. Use to cast, verify, frog, and weave task harnesses.