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 endpoint-validatorgit 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/endpoint-validator)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/endpoint-validator"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/endpoint-validator/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/endpoint-validator"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/endpoint-validator.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.01107 |
| Opus 5.5 | $0.00006 | $0.00443 |
| Sonnet 5.5 | $0.00003 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
endpoint-validator 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| All endpoints timeout | Wrong host or proxy issue | `curl -v` a single endpoint | How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Endpoint Validator Skill
Deterministic HTTP endpoint validation: discover config, test each endpoint against expectations, report pass/fail with CI-compatible exit codes.
Deep References
Load on demand when the signal matches.
| Signal | Reference | Content |
|---|---|---|
| Security header WARNs, HSTS/CSP/X-Frame | references/security-headers.md |
Header checks, required values, remediation |
| Config errors, hardcoded IPs, timeouts | references/endpoint-config-preferred-patterns.md |
Configuration failure modes and fixes |
| 401/403 failures, auth patterns | references/auth-endpoint-patterns.md |
Bearer, API-key, cookie auth validation |
Instructions
Phase 1: DISCOVER
Read repository CLAUDE.md for base URL conventions or env var names.
Search for endpoint config in order: endpoints.json in project root,
tests/endpoints.json, inline specification from user. Prefer version-controlled
config over ad-hoc lists.
Config shape:
{
"base_url": "http://localhost:8000",
"endpoints": [
{"path": "/health", "expect_status": 200},
{"path": "/api/v1/users", "expect_key": "data", "timeout": 10},
{"path": "/api/v1/search?q=test", "max_time": 2.0}
]
}
Endpoint fields: path (required), expect_status (default 200),
expect_key (top-level JSON key), timeout (default 5s), max_time (SLOW
threshold), method (default GET), headers (per-endpoint).
Rules:
- Warn before POST/PUT/DELETE against production base URLs.
- Use hostnames or
${ENV_VAR}inbase_url, not hardcoded IPs. - Confirm base URL reachable before the full suite.
Gate: config parsed, base URL reachable, at least one endpoint defined.
Phase 2: VALIDATE
Execute, do not reason. Run the request. Paste the exit code and output.
Test endpoints sequentially. For each:
- Send request with configured method and timeout.
- Check status code against
expect_status. Mismatch -> FAIL. - If
expect_keyset, parse JSON and check key exists. Missing/invalid -> FAIL. - If
max_timeset and elapsed exceeds it -> SLOW. - On non-localhost URLs, check security headers (HSTS, CSP, X-Content-Type-Options, X-Frame-Options). Missing -> WARN (not FAIL). Skip HSTS on HTTP-only base URLs. Skip X-Frame-Options if CSP has
frame-ancestors.
What ships with it
3 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.
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 Changed · -91 lines · +7 tokens per session 8c5222eb731c
- 1mo ago Changed · -124 lines b2a6f69eecc4
- 1mo ago First seen · 250 lines · 15 tokens per session scan A 4ce08bd4748c
endpoint-validator is a skill published in the GitHub repository notque/vexjoy-agent (443 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,107 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-03.
Other skills, from other repositories
api-testing
Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java). Use for standalone API tests covering schemas, auth, status/error handling, pagination, idempotency, rate limits, or contract checks; not for browser E2E specs. Keywords: REST, GraphQL, API contract, schema…
web-mocks-msw
MSW handlers, browser/server workers, test data. Use when setting up API mocking for development or testing, creating mock handlers with variants, or sharing mocks between browser and Node environments.
thirdparty-api-integration-test
Create and run gated Go integration tests for third-party APIs with real external calls, strict configuration gates, bounded timeouts, and safe runtime controls. Use for vendor/client contract verification and failure triage.
api-test-suite-builder
Generate API test suites from route definitions across frameworks: auth, input validation, contract, k6 load testing, mocking, and OpenAPI-driven generation. Use when adding new APIs, auditing test coverage, or building regression suites.
firebase-development-add-feature
This skill should be used when adding features to existing Firebase projects. Triggers on "add function", "create endpoint", "new tool", "add api", "new collection", "implement", "build feature". Guides TDD workflow with test-first development, security rules, and emulator verification.
firebase-development-add-feature
This skill should be used when adding features to existing Firebase projects. Triggers on "add function", "create endpoint", "new tool", "add api", "new collection", "implement", "build feature". Guides TDD workflow with test-first development, security rules, and emulator verification.