Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/intelligence-engineer/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/intelligence-engineer)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/intelligence-engineer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/intelligence-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/intelligence-engineer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/intelligence-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 50 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00000 | $0.03548 |
| Opus 5.5 | $0.00000 | $0.01419 |
| Sonnet 5.5 | $0.00000 | $0.00710 |
| Haiku 4.5 | $0.00000 | $0.00355 |
Grade A, and why
intelligence-engineer 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 1mo 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligence Engineer
VNX-specific domain expert for the intelligence system, central state, and dispatch lifecycle.
Core Mission
VNX has a sprawling but specific data model: dispatches flow through a runtime coordination DB, generate receipts and events, get archived, and feed back into a quality intelligence DB that informs future dispatch decisions. Most "intelligence not working" or "central state weird" bugs are NOT generic database bugs — they're domain bugs in VNX-specific code paths.
This skill exists alongside database-engineer (which covers SQLite mechanics generically). Use database-engineer for migration/schema/UPSERT work; use this skill when the question requires knowing which VNX table holds what, and why.
When to Use
- Editing or designing schemas in
schemas/quality_intelligence.sql,schemas/runtime_coordination_v*.sql, or any0010_…/0015_…migration - Touching
scripts/quality_db_init.py,scripts/lib/coordination_db.py, or any module that initializes / queries central state - Working with intelligence injection:
scripts/lib/intelligence_*,scripts/build_t0_state.py,scripts/lib/intelligence_injection.py - Debugging "code_snippets show wrong project", "dispatches missing from T0 state", "success_patterns not retrieved", "central DB query returns nothing"
- Querying central DB for cross-project insights (federation, aggregation, analytics)
- Designing a new intelligence-feeding mechanism (e.g. new event type → injection rule)
- Modifying any code that touches the project_id flow (registry → import → query → injection)
STEP 0 — Foundational Check (Mandatory)
BEFORE proposing any design, fix, or implementation:
- Consult relevant ADRs in
docs/governance/decisions/. Special attention to:- ADR-005 (NDJSON audit ledger as primary observability)
- ADR-007 (multi-tenant project_id stamping; composite keys for central state DBs)
- ADR-010 (subprocess adapter as canonical Claude routing) List any ADR that applies to the task and how it constrains your solution.
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.
- 1mo ago First seen · 245 lines · 0 tokens per session scan A c5d328f683e9
intelligence-engineer is a skill published in the GitHub repository Vinix24/vnx-orchestration (62 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,548 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
oma-backend
Implement server APIs, authentication, and application data access. Schema modeling and query tuning use oma-db.
shared-mutable-index-rmw-race-use-marker-blob-per-item
Designing a shared "who is active / recent items" index that concurrent producers write to: one mutable list silently loses entries. Write one marker per item.
api-data-model-design
Design.
build-api
Build backend API endpoints, services, and database changes. Use for backend-only work like new API routes, business logic, database schema changes, or microservice patterns. Activates the Architecture Council for significant API decisions.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
api-design-reviewer
Expert API design reviewer for REST, GraphQL, and gRPC APIs. Analyzes API designs for security, performance, consistency, scalability, and maintainability. Use when designing new APIs, reviewing API proposals, auditing existing endpoints, or before major API releases. Covers authentication, error handling, pagination…