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 assessmentgit 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/assessment)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/assessment"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/assessment/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/notque/vexjoy-agent/assessment"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/assessment.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00029 | $0.03519 |
| Opus 5.5 | $0.00012 | $0.01408 |
| Sonnet 5.5 | $0.00006 | $0.00704 |
| Haiku 4.5 | $0.00003 | $0.00352 |
Grade A, and why
assessment scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`sqlite3 "SELECT ..."`, `curl -s` (GET only), `date`, `env`. How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assessment Skill
Seven modes for read-only analysis and decision support. Match the request to a mode, then follow that mode's phases.
Mode Selection
| Request pattern | Mode |
|---|---|
| Inspect, browse, explore without changing | Read-Only Inspection |
| Onboard, overview, summarize repo, codebase structure | Codebase Overview |
| Repo value analysis, compare repos, what can we learn | Repo Value Analysis |
| Service status, health check, uptime, validate endpoints | Service Health Check |
| Consult on ADR, challenge design, architecture consultation | ADR Consultation |
| Help me decide, decision matrix, pros/cons, trade-offs | Decision Scoring |
| Critique ideas, devil's advocate, stress test, roast | Multi-Persona Critique |
Final report. When the report synthesizes two or more dispatched agents' outputs (Repo Value Analysis, ADR Consultation, Multi-Persona Critique, Codebase Overview deep-dives), run one self-review pass on the draft before delivery: skills/shared-patterns/report-self-review.md (separate dispatch, model: opus).
Read-Only Inspection
Safe exploration without modifying files or system state.
Phase 1: SCOPE
Parse the request. Determine target scope (file, directory, service, system-wide). Clarify before proceeding if scope could match dozens of results.
Phase 2: GATHER
Use read-only tools only.
Allowed: ls, find, wc, du, df, file, stat, ps, top -bn1,
uptime, free, pgrep, git status/log/diff/show/branch,
sqlite3 "SELECT ...", curl -s (GET only), date, env.
Forbidden: mkdir, rm, mv, cp, touch, chmod, chown,
git add/commit/push, file writes, INSERT/UPDATE/DELETE/DROP,
npm/pip/apt install, kill, systemctl restart.
Phase 3: REPORT
Lead with the answer. Show supporting evidence. List files examined. All claims must cite evidence.
What ships with it
26 files 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.
- references/adr-consultation/agent-prompts.md 4.0 KB
- references/adr-consultation/consultation-patterns.md 10 KB
- references/adr-consultation/consultation-preferred-patterns.md 8.9 KB
- references/adr-consultation/error-handling.md 9.0 KB
- references/codebase-overview/examples-and-errors.md 7.0 KB
- references/codebase-overview/exploration-strategies.md 5.5 KB
- references/codebase-overview/report-template.md 4.8 KB
- references/codebase-overview/statistical-analysis-examples.md 13 KB
- references/codebase-overview/statistical-metrics-catalog.md 7.8 KB
- references/codebase-overview/statistical-phase-details.md 6.0 KB
- references/codebase-overview/statistical-three-lenses.md 9.1 KB
- references/decision-helper/decision-archetypes.md 7.4 KB
- references/decision-helper/decision-preferred-patterns.md 8.0 KB
- references/multi-persona-critique/examples-and-errors.md 6.6 KB
- references/multi-persona-critique/personas.md 12 KB
- references/multi-persona-critique/roast.md 12 KB
- references/multi-persona-critique/synthesis-template.md 7.0 KB
- references/repo-value-analysis/phase7-implement-template.md 6.4 KB
- references/service-health-check/auth-endpoint-patterns.md 7.6 KB
- references/service-health-check/cve-source-check.md 5.4 KB
- references/service-health-check/endpoint-config-preferred-patterns.md 6.7 KB
- references/service-health-check/endpoint-validator.md 8.9 KB
- references/service-health-check/security-headers.md 6.2 KB
- scripts/cartographer_omni.py 104 KB runs code
- scripts/cartographer_ultimate.py 16 KB runs code
- scripts/cartographer.py 19 KB runs code
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.
- yesterday Changed · +260 lines · -12 tokens per session e82233bf6cf3
- 26d ago Changed · -256 lines · +12 tokens per session f45df9666800
- 27d ago First seen · 369 lines · 29 tokens per session scan A 7fe83080368a
assessment is a skill published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 3,519 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-20.
Other skills, from other repositories
beehave
Use when using the Beehave addon — pure-GDScript behavior trees with composites, decorators, leaves, a blackboard, and a visual runtime debugger.
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
asc-crash-triage
Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
om-auto-fix-issue
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr, om-auto-qa-pr for UI fixes) or the feature…
deliver-edge-cases
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…