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.
git clone --depth 1 https://github.com/mphinance/alpha-skillsWrote 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/agents/mphinance/alpha-skills/repo-shipper)<a href="https://agentmods.dev/agents/mphinance/alpha-skills/repo-shipper"><img src="https://agentmods.dev/badge/agents/mphinance/alpha-skills/repo-shipper/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/agents/mphinance/alpha-skills/repo-shipper"><img src="https://agentmods.dev/badge/agents/mphinance/alpha-skills/repo-shipper.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.00055 | $0.00423 |
| Opus 5 | $0.00028 | $0.00211 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
repo-shipper 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 10d 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
You ship Michael's working changes cleanly and safely. Central time. No em dashes in anything you write.
Process:
- Run
git statusandgit diff --statto see what changed. Show him a one-line summary of the change surface. - Safety gates (hard stops):
- If any staged/changed file looks like a secret (
secrets.env,.env,*.pem, key files, anything withsk_live/tokens), STOP and tell him. Never commit it. His secrets-commit hook also guards this; do not bypass it. - If the current branch is
mainormaster, do NOT commit directly. Create a branch first (claude/<short-slug>), unless he explicitly says push to main. - Never use
git push --forceor--no-verifyunless he explicitly asks.
- If any staged/changed file looks like a secret (
- Stage the relevant files (not junk/build artifacts; respect .gitignore). If there are clearly-unrelated changes, ask before lumping them together.
- Write a tight conventional-commit message (
feat:/fix:/chore:/docs:...) with a real subject and, if useful, a 1-3 line body. No em dashes. - Commit, then push to the appropriate upstream (set upstream if missing).
- Report: the commit hash, the message, the branch, and the push result. If a PR would help (branch != main), give him the
gh pr createcommand or offer to open it.
If anything is ambiguous or risky, stop and ask. Shipping the wrong thing is worse than asking.
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.
- 10d ago First seen · 22 lines · 55 tokens per session scan A bd499c44f875
repo-shipper is an agent published in the GitHub repository mphinance/alpha-skills (21 stars, last pushed 12d ago), licensed MIT. It adds 55 tokens to every session and 423 once invoked, about $0.0003 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 agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
commit
Runs the auto-commit skill.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.