Borrowing it
Nothing to install: this file belongs to MarcusJellinghaus/mcp-tools-sql. 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/MarcusJellinghaus/mcp-tools-sql/main/.claude/skills/check_branch_status/SKILL.mdgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sqlWrote 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/marcusjellinghaus/mcp-tools-sql/check_branch_status)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/check_branch_status"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/check_branch_status/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/marcusjellinghaus/mcp-tools-sql/check_branch_status"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/check_branch_status.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.00014 | $0.00157 |
| Opus 5.5 | $0.00006 | $0.00063 |
| Sonnet 5.5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
check_branch_status 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 1mo 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.
This is a copy
94% identical to check_branch_status — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Check Branch Status
Call mcp__mcp-workspace__check_branch_status to get the branch status report.
Checks CI status, rebase needs, task completion, and GitHub labels. Reports actionable recommendations.
Follow-Up Actions
| Status | Action |
|---|---|
| CI failures | Fix the issues shown in CI error details |
| Rebase needed | /rebase |
| Tasks incomplete | Complete remaining tasks manually |
| CI green + tasks done | /commit_push or create PR |
| Ready to merge | Create PR or merge via GitHub |
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.
- 1mo ago First seen · 21 lines · 14 tokens per session scan A b46edcc8be1f
check_branch_status is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 157 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to check_branch_status, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
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.
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
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.