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/foru17/neko-master/verify-changesnpx skills add foru17/neko-master --skill verify-changesgit clone --depth 1 https://github.com/foru17/neko-masterWrote 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/foru17/neko-master/verify-changes)<a href="https://agentmods.dev/skills/foru17/neko-master/verify-changes"><img src="https://agentmods.dev/badge/skills/foru17/neko-master/verify-changes.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00563 |
| Opus 5 | $0.00023 | $0.00282 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
verify-changes 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 4d 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
Verify Changes
Run the smallest check set that covers what you touched. All commands run from the repo root unless noted.
By touched area
apps/collector (backend)
pnpm --filter @neko-master/collector exec tsc --noEmit
pnpm --filter @neko-master/collector test
Single test file / case (much faster while iterating):
pnpm --filter @neko-master/collector test -- src/modules/auth/auth.service.test.ts
pnpm --filter @neko-master/collector test -- -t "should validate token format"
Lint (CI-relevant; console.log is forbidden in collector source — use console.info/warn/error):
pnpm --filter @neko-master/collector lint
apps/web (frontend)
pnpm --filter @neko-master/web exec tsc --noEmit
pnpm --filter @neko-master/web lint
For production-impacting changes (new routes, error boundaries, next.config, i18n files) also run the full build — it catches what tsc alone misses:
pnpm --filter @neko-master/web exec next build
packages/shared
Shared types are consumed by both apps — verify both compile:
pnpm --filter @neko-master/shared build
pnpm --filter @neko-master/collector exec tsc --noEmit
pnpm --filter @neko-master/web exec tsc --noEmit
apps/agent (Go probe)
cd apps/agent
go vet ./... && go build ./... && go test ./...
sh -n nekoagent && sh -n install.sh
Checklist before commit
- Checks above pass for every touched area
- New behavior has a test (collector uses Vitest; see
src/__tests__/helpers.tsforcreateTestDatabase()/createTestBackend()) - UI changes: both locales translated and dark mode checked (see the
ui-conventionsskill) - DB writes/schema touched: run the
add-stats-dimension/db-conventionschecklists
Note: .husky/pre-push runs collector tsc --noEmit + web build when pushing to main — running them yourself first avoids a slow failed push.
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.
- 4d ago First seen · 71 lines · 47 tokens per session scan A 2de8c7a2bdc8
verify-changes is a skill published in the GitHub repository foru17/neko-master (3,861 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 563 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-30.
Other skills, from other repositories
data-viz-renderer
Generate self-contained HTML/SVG infographics from JSON data, including stat cards, bar charts, flow diagrams, and mixed dashboards. Offers 8 color palettes and built-in icons with no external dependencies. Triggered when users request data visualization, infographics, charts, or dashboards.
grafana-dashboard
Create, view, and manage Grafana dashboards with panels and datasources.
superset-dashboard
Create, view, and manage Superset dashboards with charts and datasets.
chart-designer
Design effective data visualizations and charts. Generate chart configurations for ECharts, Chart.js, and other libraries. Create dashboards and reports.
webnovel-dashboard
启动只读小说管理面板，查看项目状态、实体图谱与章节内容。.
building-incident-response-dashboard
Builds real-time incident response dashboards in Splunk, Elastic, or Grafana to provide SOC analysts and leadership with situational awareness during active incidents, tracking affected systems, containment status, IOC spread, and response timeline. Use when IR teams need unified visibility during incident…