Borrowing it
Nothing to install: this file belongs to judell/bram. 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/judell/bram/main/.claude/skills/loose-ends/SKILL.mdgit clone --depth 1 https://github.com/judell/bramWrote 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/judell/bram/loose-ends)<a href="https://agentmods.dev/skills/judell/bram/loose-ends"><img src="https://agentmods.dev/badge/skills/judell/bram/loose-ends.svg" alt="Measured on agentmods" 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.00034 | $0.00458 |
| Opus 5 | $0.00017 | $0.00229 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
loose-ends 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 6d 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
Loose ends
Survey this repository's git state and give the user a tight, scannable summary of everything that is loose and may need attention. Read-only — inspect and report; do not stage, commit, push, stash, or modify anything.
If an argument is provided, focus the summary on that path or area (e.g. only
loose ends touching src-tauri/); otherwise cover the whole repo.
Gather
Run these (all read-only):
git status --short --branch— uncommitted + untracked changes, plus the branch's ahead/behind vs its upstream.git log --oneline @{u}..HEAD— commits not yet pushed. If the branch has no upstream, say so (there is nothing to push against) and skip this.git log --oneline -5— recent history, for context.git stash list— stashed work.git branch -vv— local branches and their tracking / ahead-behind.
Report
A short summary in Markdown, including only the non-empty groups:
- Unpushed commits — count, then one line each (short SHA + subject).
- Uncommitted changes — modified / added / deleted tracked files.
- Untracked files — new files not yet added; flag anything that looks like it should be committed versus scratch/output.
- Stashes — any stash entries.
- Other — detached HEAD, local branches ahead of their upstream, etc.
End with a one-line bottom line: either "clean and pushed" or the single most important loose end to deal with next.
Do not propose or perform commits, pushes, or stashes unless the user asks — just surface the state.
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.
- 6d ago First seen · 46 lines · 34 tokens per session scan A 83e507ed55bf
loose-ends is a skill published in the GitHub repository judell/bram (46 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 458 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
将 Comet GitHub 维护请求路由到基于证据的 PR 审阅、Issue 分诊、本地想法收集、CI 诊断或 Issue 实施流程。用户提到 Comet GitHub Issue/PR 但未指定流程，或询问下一步如何处理时使用。.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".