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/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/judell/bram/loose-ends"><img src="https://agentmods.dev/badge/skills/judell/bram/loose-ends.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 7 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.5 | $0.00014 | $0.00183 |
| Sonnet 5.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 2mo 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.
- 2mo ago First seen · 46 lines · 34 tokens per session scan A 83e507ed55bf
loose-ends is a skill published in the GitHub repository judell/bram (57 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 458 once invoked, about $0.0001 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-08-30.
loose-ends compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| loose-endsjudell/bram | Skill | 57 | yesterday | Apache-2.0 | A | 34 | Claude Code |
| merge-batchdiegosouzapw/OmniRoute | Skill | 83k | 5d ago | MIT | A | 46 | Claude Code |
| prowler-commitprowler-cloud/prowler | Skill | 15k | yesterday | Apache-2.0 | A | 44 | Claude Code, Codex |
| gh-auth-isolationgithub/gh-aw | Skill | 5.6k | yesterday | MIT | A | 20 | Claude Code, Codex |
| github-skillzeenie-ai/OpenCompany | Skill | 1.1k | yesterday | MIT | A | 51 | Claude Code |
| comet-githubrpamis/comet | Skill | 3.3k | yesterday | MIT | A | 72 | Claude Code, Codex |
| release-helperSahir619/fable-method | Skill | 2.3k | 1mo ago | MIT | A | 43 | Claude Code |