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 skills add MarcusJellinghaus/mcp-tools-py --skill check_branch_statusgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-pyWrote 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-py/check_branch_status)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/check_branch_status"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/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-py/check_branch_status"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/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.00161 |
| Opus 5 | $0.00007 | $0.00081 |
| Sonnet 5 | $0.00003 | $0.00032 |
| 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 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.
This is a copy
95% identical to check_branch_status — 5 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 the mcp__mcp-workspace__check_branch_status MCP tool with no arguments and report its output.
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.
- 6d ago Changed · -1 lines 5b86f461cf50
- 10d ago First seen · 23 lines · 14 tokens per session scan A 3f9d75ceb757
check_branch_status is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 161 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to check_branch_status, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
metagit-cli
CLI-only shortcuts for metagit agents — workspace catalog, discovery, prompts, sync, layout, and config. Use instead of MCP or HTTP API when operating from a shell or agentmode session.
metagit-context-pack
Token-efficient workspace onboarding via tiered context packs — map, repo cards, session digest, objectives, approvals, repomix profiles. Use at session start or when scoping work in a metagit-managed workspace.
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-agent-access
Optimize any repository for minimal-token agent onboarding — llms.txt, AGENTS.md, hidden HTML agent blocks, docs/agents.md. Use when asked to improve agentic access, agent metadata, llms.txt, or run the agent-access optimizer subagent on a project.
metagit-agent-coordination
Isolate concurrent agents with RFC-0007 ACL primitives: allocate agent/ branches, acquire branch leases, create exclusive git worktrees, and declare advisory file claims. Use when launching multiple agents, avoiding shared checkouts, preventing branch collisions, or coordinating file ownership before coding. Distinct…