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/inspectnpx skills add jun0-ds/sonmat --skill inspectgit 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.00050 | $0.02448 |
| Opus 5 | $0.00025 | $0.01224 |
| Sonnet 5 | $0.00010 | $0.00490 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
inspect 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 2d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect — Discovery-Led Depth
Inspect is not a mode. It is a set of checks that fire in response to a specific discovery. The discovery-led principle: active discovery pulls depth in, not the other way around — depth is not a dial you turn up before knowing what you are looking at.
When a System 1 signal (see Triggers below) surfaces, inspect pulls System 2 checks scoped to that specific signal. One discovery → depth on that discovery → checks resolve → back to default operation. No "inspect on / inspect off" state.
Manual invocation (/inspect) is still available when the user wants to force a depth pass without waiting for an auto-detected trigger — but even then, it runs once for the current change and exits.
What inspect does when triggered
Scope of a single depth pass
| Default operation | Depth pass fires |
|---|---|
| Changed files only | Changed files + direct dependents |
| Tests pass? | Tests pass + are tests covering the right cases? |
| Does it work? | Does it work + what could it break? |
The depth scope is bounded by the trigger. A "shared utility edit" trigger pulls depth into its dependents; it does not turn on "inspect mode" for the rest of the session.
Additional checks (on top of guard)
Four check types. A depth pass does not run all four by default — which check fires is determined by the trigger. Running all four regardless of trigger would violate the discovery-led principle (depth chosen without a specific discovery).
- Dependency trace: For each modified function/module, list callers and downstream consumers. Flag any that might behave differently.
- Side effect scan: State changes (DB writes, file writes, env mutations, global state) — are they intended? Are they reversible?
- Assumption audit: What does this code assume about its inputs, environment, or execution order? Are those assumptions documented or tested?
- Rollback viability: If this change goes wrong in production, how do you undo it? Is there a migration, a flag, a revert path?
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.
- 2d ago First seen · 168 lines · 50 tokens per session scan A 8786c04530f6
inspect is a skill published in the GitHub repository jun0-ds/sonmat (6 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 50 tokens to every session and 2,448 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-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"/"找选题"。.