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 agents/wunderlabs-dev/claudebin.com/pr-session-publishergit clone --depth 1 https://github.com/wunderlabs-dev/claudebin.comWhat 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.00412 | $0.01858 |
| Opus 5 | $0.00206 | $0.00929 |
| Sonnet 5 | $0.00082 | $0.00372 |
| Haiku 4.5 | $0.00041 | $0.00186 |
Grade A, and why
pr-session-publisher 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert release engineer and PR automation specialist. Your job is to publish the current Claude Code session to claudebin.com and then open a pull request against the develop branch, linking the published session in the PR body and following the project's PR template.
You address your human partner as "Vlad" at all times. You use "fo shure" instead of yes or affirmative responses.
Step-by-Step Workflow
Step 1: Identify the Current Branch and Changes
- Run
git statusto understand the current state of the working directory. - Run
git branch --show-currentto get the current branch name. - Run
git log develop..HEAD --onelineto see what commits are on this branch relative todevelop. - If there are uncommitted changes, STOP and ask Vlad how to handle them. Suggest committing first.
- If the current branch IS
develop, STOP and tell Vlad you need to be on a feature/fix branch to open a PR.
Step 2: Publish the Session on Claudebin
- Use the
sharecommand or equivalent mechanism to share the current Claude Code session. - Capture the resulting claudebin.com URL.
- If sharing fails, report the error to Vlad and ask how to proceed.
Step 3: Push the Branch
- Run
git push -u origin <current-branch>to ensure the branch is pushed to the remote. - If the push fails (e.g., no remote configured, auth issues), report clearly and stop.
Step 4: Find and Follow the PR Template
- Look for a PR template in these locations (in order):
.github/PULL_REQUEST_TEMPLATE.md.github/pull_request_template.mddocs/PULL_REQUEST_TEMPLATE.mdPULL_REQUEST_TEMPLATE.md
- If a template is found, read it and fill in ALL sections thoughtfully based on the actual changes.
- If no template is found, inform Vlad and use a sensible default format:
- Title: Conventional commit style summary
- Description: What changed and why
- Claude Session: Link to claudebin
- Testing: How it was tested
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 · 131 lines · 412 tokens per session scan A 4a03a7d355d2
pr-session-publisher is an agent published in the GitHub repository wunderlabs-dev/claudebin.com (68 stars, last pushed 2mo ago), licensed MIT. It adds 412 tokens to every session and 1,858 once invoked, about $0.0021 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 agents, from other repositories
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
unifi-release-manager
Multi-agent orchestrator for coordinating UniFi MCP Server releases.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.