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 skills add notque/vexjoy-agent --skill integration-checkergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/integration-checker)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/integration-checker"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/integration-checker.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00012 | $0.00879 |
| Opus 5 | $0.00006 | $0.00439 |
| Sonnet 5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
integration-checker 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration checker
Check that components are connected and receive real data. A function can pass unit tests yet never be called; an endpoint can exist without being registered.
This skill reads and reports. Return fixes to the active implementation task or feature-lifecycle; do not create another approval round when fixes are already authorized.
Reference loading
Load references/wiring-checks.md for language detection, export exclusions, wiring states, data-flow failures, contract patterns, and the requirements map.
Phase 0: PRIME
Read repository instructions. In a feature pipeline, use .feature/state/implement/ to scope changed and added files. Otherwise use the requested path or diff; a requested full audit covers all source files. If the implementation artifact is missing, use the diff and state the gap.
Detect every language in scope. Reuse existing integration evidence for unchanged connections; trace affected producers and consumers beyond the diff where needed.
Gate: Scope and languages are known.
Phase 1: EXPORT/IMPORT MAP
Inventory public symbols using language-aware searches:
- Go: exported package functions, types, constants, variables, and methods.
- Python: module definitions,
__all__, and__init__.pyre-exports. - TypeScript/JavaScript: named/default exports and barrel re-exports.
Exclude dependencies, generated files, build output, fixtures, and repository metadata. Apply the reference's exceptions for public library APIs, plugin contracts, framework entrypoints, and other legitimate external consumers before calling a symbol orphaned.
For each symbol, record file, name, kind, and line. Find imports and actual usage; an import alone does not establish wiring. Classify as ORPHANED, IMPORTED_NOT_USED, or WIRED using the reference. Report failures first; show successful connections only in verbose mode.
Gate: Every in-scope symbol has a status or an explicit unresolved limitation.
Phase 2: DATA FLOW AND CONTRACT CHECK
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -133 lines 2df7a3a9d7ab
- 4d ago First seen · 219 lines · 12 tokens per session scan A 340512ff7bff
integration-checker is a skill published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 879 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
insforge-debug
Use when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denial, realtime channel issues, slow query on one endpoint, edge function or Vercel deploy failure), proactive audits…
firebase-development-debug
This skill should be used when troubleshooting Firebase emulator issues, rules violations, function errors, auth problems, or deployment failures. Triggers on "error", "not working", "debug", "troubleshoot", "failing", "broken", "permission denied", "emulator issue".
error-recovery-patterns
What to do when things break.
arcana
In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions…
frappe-errors-api
Use when debugging or handling API errors in Frappe/ERPNext v14/v15/v16. Prevents silent failures and wrong HTTP status codes in REST endpoints. Covers 401 Unauthorized (wrong token format, expired OAuth), 403 Forbidden (missing @whitelist, allowguest needed), 404 Not Found (wrong endpoint URL), 417 Expectation Failed…
frappe-errors-hooks
Use when debugging hooks.py errors in Frappe/ERPNext. Covers hook not firing (typo, wrong dict structure), circular imports, appincludejs path errors, schedulerevents not running, docevents on wrong DocType, permissionqueryconditions SQL errors, overridedoctypeclass import failures, extenddoctypeclass [v16+]…