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 jessepinkman9900/claude-second-brain --skill releasegit clone --depth 1 https://github.com/jessepinkman9900/claude-second-brainWrote 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/jessepinkman9900/claude-second-brain/release)<a href="https://agentmods.dev/skills/jessepinkman9900/claude-second-brain/release"><img src="https://agentmods.dev/badge/skills/jessepinkman9900/claude-second-brain/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/jessepinkman9900/claude-second-brain/release"><img src="https://agentmods.dev/badge/skills/jessepinkman9900/claude-second-brain/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.00075 | $0.01177 |
| Opus 5 | $0.00037 | $0.00589 |
| Sonnet 5 | $0.00015 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Orchestrates a complete release for claude-second-brain:
- Resolve the target version.
- Run
/update-workflowsto catchpack-test.ymldrift before CI sees it. - Commit any workflow edits.
- Run
/update-docsso the docs site and ship log reflect what's shipping (ship log entry uses the target version). - Commit the docs changes.
- Run
/package-releaseto bumppackage.json, commit, push, and open the PR.
The result is one PR containing up to three commits (workflows → docs → version) so CI passes on first push.
If you only want one half, run /update-workflows, /update-docs, or /package-release directly — each is usable standalone.
Preconditions
- Current branch has commits relative to
main. - Working tree is otherwise clean (no unrelated staged/unstaged changes — the orchestrator will commit anything staged).
Steps
Step 1 — Resolve target version
Read the current version:
cat package.json | grep '"version"'
Apply the same semver logic /package-release uses:
| Signal | Bump |
|---|---|
| Breaking CLI / template changes, or commits containing "breaking" | major |
| New skills, new CLI flags, new template sections, or new behavior | minor |
| Bug fixes, docs, refactors only | patch |
If the user passed an argument (/release patch, /release 0.2.0, etc.) use it directly.
Otherwise summarize the diff (git log main..HEAD --oneline + git diff main...HEAD --stat), suggest a bump, and ask the user to confirm. Do not continue until confirmed.
Record the resolved version as vX.Y.Z for the rest of the flow.
Step 2 — Run /update-workflows
Invoke the update-workflows skill. When it asks for approval of its proposal, forward it to the user and wait.
If the audit reports "pack-test is in sync — nothing to update," skip to Step 4.
Let /update-workflows apply its edits.
Step 3 — Commit workflow changes
If /update-workflows modified any files (check git status):
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.
- 9d ago First seen · 114 lines · 75 tokens per session scan A 3009a1c99ee6
release is a skill published in the GitHub repository jessepinkman9900/claude-second-brain (47 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 1,177 once invoked, about $0.0004 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…