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/jun0-ds/sonmat/punchnpx skills add jun0-ds/sonmat --skill punchgit clone --depth 1 https://github.com/jun0-ds/sonmatWhat 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.00048 | $0.03371 |
| Opus 5 | $0.00024 | $0.01685 |
| Sonnet 5 | $0.00010 | $0.00674 |
| Haiku 4.5 | $0.00005 | $0.00337 |
Grade A, and why
punch 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Punch — Punch List Before Delivery
Like a construction punch list: walk the finished building and note everything that's missing or incomplete before handoff.
Not "does this work?" (that's guard/inspect) but "what was supposed to exist that doesn't?"
Invoke: /punch (runs once for the current scope, reports, and exits — not a mode). Manual-only; punch does not auto-activate.
Why this exists
Vibe coding skips the spec. That's a feature, not a bug — but it removes the safety net that specs provided: a shared checklist of "everything that should exist."
Traditional collaboration solves this with requirements docs, design reviews, and QA teams — multiple humans independently checking completeness. In AI-human collaboration, there's no second human. This skill fills that gap.
Research basis: 40-55% of all implementation errors are omissions — things that should exist but don't. Another 20-25% are ambiguity — things that exist but in the wrong form. Only 10-15% are outright wrong. The biggest ROI is finding what's missing, not what's broken.
Method: Reconstruct + Checklist, then Diff
Two complementary lenses:
- Reconstruct: derive what should exist from intent and implementation (catches project-specific gaps)
- Domain checklist: apply known must-haves for this type of work (catches gaps the user also forgot)
Neither alone is sufficient. Reconstruction misses what nobody thought of. Checklists miss what's unique to this project. Together they cover both.
Phase short-circuit — residue-only fast path
If punch was invoked as /punch residue, or if the trigger was Structural removal or Rename and the user has not requested reconstruction, skip Phase 1 and Phase 2 entirely and jump to Phase 3's Residue-free check. Residue detection is mechanical grep — it does not need intent reconstruction or domain checklists. Running Phase 1 dialogue for pure residue cleanup is overhead that undermines the point of having a fast path for structural changes.
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.
- 3d ago First seen · 241 lines · 48 tokens per session scan A c5d8de2cabf5
punch is a skill published in the GitHub repository jun0-ds/sonmat (6 stars, last pushed 5d ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 3,371 once invoked, about $0.0002 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-31.
Other skills, from other repositories
mundo
MUNDO - THE EMPEROR. The ultimate AI learning engine. No triggers needed. Every task, Mundo takes over. Consults ALL AIs, crawls ALL web, integrates ALL solutions, saves ALL useful skills. Self-evolving. Collective consciousness. Infinite growth. Uses Three Departments and Six Ministries system to rule all skills.…
llm-app-patterns
Production-ready patterns for building LLM applications, inspired by Dify and industry best practices.
kpi-dashboard-design
Comprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions.
neat-freak
End-of-session knowledge cleanup with OCD-level rigor — reconciles project docs (CLAUDE.md, README.md, docs/) and agent memory against the code so nothing rots. 会话结束后对项目文档和记忆进行洁癖级审查与同步。MUST trigger when the user says: "sync up", "tidy up docs", "update memory", "clean up docs", "/sync", "/neat", "同步一下", "整理文档"…
resume-builder
制作/优化专业简历（HTML格式）。触发词：简历、resume、CV、求职、找工作、投简历。自动加载，白底专业风格，禁止深色主题和过度设计。.
cheat-trends
从配置的热点源（HN / Reddit / YouTube trending / B 站热门 / 等）抓今天的热门话题，去重 + 粗打分 + 写入 candidates.md。绝大部分人没有候选池——这是让"我没素材"问题在 onboarding 第二步就消失的钥匙。触发词："抓热点"/"fetch trends"/"今天有什么可做的"/"trending now"/"找选题"。.