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/alphabitcore/nexus-gateway/test-allnpx skills add AlphaBitCore/nexus-gateway --skill test-allgit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWrote 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/alphabitcore/nexus-gateway/test-all)<a href="https://agentmods.dev/skills/alphabitcore/nexus-gateway/test-all"><img src="https://agentmods.dev/badge/skills/alphabitcore/nexus-gateway/test-all.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.1 | $0.00167 | $0.01441 |
| Opus 5 | $0.00084 | $0.00720 |
| Sonnet 5 | $0.00033 | $0.00288 |
| Haiku 4.5 | $0.00017 | $0.00144 |
Grade A, and why
test-all 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 6d 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.
adding "let me also curl X to verify" steps to this skill, that How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test All
Drives tests/run-all.sh end-to-end and reports back. This is the
recommended entry point after any non-trivial code change — it covers
every layer of the test program (docs/developers/architecture/cross-cutting/observability/test-harness-architecture.md) and produces
one report you can paste into a PR or hand to a reviewer.
When to use
- User typed
/test-all,/test-all --quick, or asked something like "run all tests", "regression check", "test everything", "smoke the whole system". - Right before declaring a multi-service change done.
- After a service restart or config change, to confirm everything is still wired up.
Don't use this for narrowly-scoped debugging — pick a single layer (L1 smoke, L1 Go integration, L4 UI) and run that test directly.
Inputs
| Arg | Required | Notes |
|---|---|---|
--quick |
no | Preflight + L1 smoke only (≈ 30 s, no LLM calls). Default mode. |
--full |
no | All phases including L3 AI-judge and L4 Playwright (≈ 3–5 min, costs ~5 Kimi calls). |
--phase <name> |
no | Run only one phase: smoke, go, ui, protocol, ai-judge. |
--no-preflight |
no | Skip preflight (use only when debugging the runner itself). |
If the user did not pass a flag, default to --full. The cost of one full
run (~2 ¢ in Kimi tokens, ~5 minutes wall) is worth it as a green/red
signal; downgrade to --quick only if the user asked for fast feedback.
Prerequisites
Verify before starting (the runner's own preflight will also check; we front-run these so failures surface in chat, not in a buried log):
tests/.env.localexists andNEXUS_TEST_VKis not the placeholdernvk_REPLACE_ME. If missing, instruct the user to copytests/.env.local.exampleand setNEXUS_TEST_VKto a real Nexus VK (theresearch-all-modelsVK is fine for local dev; query the DB if needed:SELECT name, "keyPrefix" FROM "VirtualKey" WHERE enabled = true AND "vkType" = 'application' LIMIT 5;).- Local services running. Quick check:
lsof -nP -iTCP:3001,3040,3050,3060 -sTCP:LISTEN. All four ports must show a listener. If any are missing, ask the user whether to start them (./scripts/dev-start.shis the canonical bootstrap) rather than launching them silently. - Postgres + Redis containers up:
docker ps --filter name=nexus-postgres --filter name=nexus-redis --format '{{.Names}}'.
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.
- 6d ago First seen · 124 lines · 167 tokens per session scan A 2a1a4d1dd841
test-all is a skill published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 4d ago), licensed Apache-2.0. It adds 167 tokens to every session and 1,441 once invoked, about $0.0008 per session on Opus 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-08-30.
Other skills, from other repositories
defenseclaw-ops
Manage DefenseClaw enterprise security - scan components, manage tool permissions, view alerts, configure guardrails.
ai-identity-platform
Structured identity management for AI agent fleets — define, govern, and audit agent personas at scale.
procurement-intelligence
Enterprise Procurement Intelligence — full lifecycle procurement expertise. Covers policy compliance, tender generation, supplier risk, budget verification, three-way matching, spend analytics, market intelligence, and procurement audit. Integrates with the Enterprise Procurement MCP Server for tool execution.
higress-update-envoy-gateway
Update Higress Envoy binary and gateway image dependencies for e2e validation. Use when Codex needs to build Envoy packages from the current Higress branch, upload those packages to higress-group/proxy releases, update Makefile.core.mk ENVOYPACKAGEURLPATTERN and ENVOYLATESTIMAGETAG, run make build-gateway-local, retag…
signal-end-to-end
Implements end-to-end signal changes spanning router config, signal extraction, CLI schema, optional bindings, router-owned metadata headers, and E2E test coverage. Use when adding a new signal type, changing signal configuration or extraction logic, updating CLI schema for signal parameters, or modifying router-owned…
plugin-end-to-end
Implements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.