jolt-atlas: Skill for Claude Code

.claude/skills/clean-branch/SKILL.md

clean-branch is a skill for Claude Code from ICME-Lab/jolt-atlas. It costs 64 tokens per session (1,069 once invoked), scanned A, original, no licence file.

A read-only check of the current Git branch against the repository's pull-request rules. It reports findings and recommends fixes without rewriting commit history.

In plain words
What is it for?
Use it to prepare, review, or clean up a branch before a pull request, following the rules in docs/pull-requests.md.
Why use it?
It helps catch branch problems before opening or updating a pull request. Because it only audits, it does not make unwanted changes to your history.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ICME-Lab/jolt-atlas's own configuration. It tells Claude Code how to work on jolt-atlas itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jolt-atlas configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ICME-Lab/jolt-atlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ICME-Lab/jolt-atlas/main/.claude/skills/clean-branch/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ICME-Lab/jolt-atlas

Made for: Claude Code.

Wrote 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.

agentmods badge for clean-branch

README.md
[![agentmods](https://agentmods.dev/badge/skills/icme-lab/jolt-atlas/clean-branch/github.svg)](https://agentmods.dev/skills/icme-lab/jolt-atlas/clean-branch)
Your own site
<a href="https://agentmods.dev/skills/icme-lab/jolt-atlas/clean-branch"><img src="https://agentmods.dev/badge/skills/icme-lab/jolt-atlas/clean-branch/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.

agentmods 80×15 button for clean-branch

Your own site · 80×15
<a href="https://agentmods.dev/skills/icme-lab/jolt-atlas/clean-branch"><img src="https://agentmods.dev/badge/skills/icme-lab/jolt-atlas/clean-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,069 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.01069
Opus 5.5 $0.00026 $0.00428
Sonnet 5.5 $0.00013 $0.00214
Haiku 4.5 $0.00006 $0.00107

Measured 4d ago against content hash f54ca8ace312, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

clean-branch 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 4d 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.

.claude/skills/clean-branch/SKILL.md · 77 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 4d ago First seen · 77 lines · 64 tokens per session scan A f54ca8ace312

Subscribe to this mod's changes

clean-branch is a skill published in the GitHub repository ICME-Lab/jolt-atlas (79 stars, last pushed 2d ago), with no licence file. It adds 64 tokens to every session and 1,069 once invoked, about $0.0003 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-10-26.

Related

Other skills, from other repositories

retentioneering-contributing

Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's…

retentioneering/retentioneering-tools · 106 tokens

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens