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 agentmods add skills/zeroclaw-labs/zeroclaw/squash-mergenpx skills add zeroclaw-labs/zeroclaw --skill squash-mergegit clone --depth 1 https://github.com/zeroclaw-labs/zeroclawWhat 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 | $0.00000 | $0.03975 |
| Opus 5 | $0.00000 | $0.01988 |
| Sonnet 5 | $0.00000 | $0.00795 |
| Haiku 4.5 | $0.00000 | $0.00398 |
Grade A, and why
squash-merge 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: squash-merge
Squash-merge a PR into zeroclaw-labs/zeroclaw master with fully preserved commit history in the squash message body. Use this skill when the user explicitly mentions squash-merging, merging a specific PR number, landing a PR, or 合入 — e.g. "squash-merge #123", "merge PR 456", "land #789", "合入 #123", "/squash-merge 123". Do not trigger on vague phrases like "ship it" or "merge it" without a PR number or clear upstream-merge context.
Related Skills
| Step | Skill | When |
|---|---|---|
| Pick / triage issues | github-issue-triage |
Backlog sweep, label issues, close duplicates |
| File a bug / feature | github-issue |
No existing issue for the work |
| Open / update PR | github-pr |
Branch is ready; needs template body and validation evidence |
| Review before merge | github-pr-review-session |
Maintainer reviewing someone else's PR |
| Land into master | this skill | PR is approved and CI is green |
End-to-End Contributor Workflow (issue → merge)
When the user asks to fix an issue and get it merged, follow this sequence:
- Read the issue —
gh issue view <N>; confirm it is still open and not already fixed onmaster. - Branch —
git checkout -b fix/<short-description>from up-to-datemaster. - Implement — minimal diff; reference canonical state (see
AGENTS.mdno-duplicate-state rule). - Validate — run
cargo fmt --all -- --check,cargo clippy --all-targets -- -D warnings,cargo test(or docs gate if docs-only). - Open PR — use the
github-prskill; body must includeCloses #<N>when the PR fully resolves the issue. - Wait for CI — before merge, confirm required checks pass (see Pre-merge CI check below).
- Squash-merge — use this skill with explicit user confirmation.
Do not skip straight to merge if no PR exists yet.
Why This Exists
GitHub's default squash merge omits the PR number from the commit subject and formats the commit body inconsistently with project conventions. Direct-pushing a squash to master bypasses the PR merge mechanism entirely: the PR shows "Closed" instead of "Merged" (no purple badge, no linked issue auto-close, no merge commit association). This skill produces both: the purple Merged badge and a conventionally formatted squash commit with full commit history in the body.
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.
- yesterday First seen · 313 lines · 0 tokens per session scan A a39864902250
squash-merge is a skill published in the GitHub repository zeroclaw-labs/zeroclaw (32,680 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,975 tokens. 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
surprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for…