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/nexus-substrate/nexus-agents/e2e-validationnpx skills add nexus-substrate/nexus-agents --skill e2e-validationgit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/e2e-validation)<a href="https://agentmods.dev/skills/nexus-substrate/nexus-agents/e2e-validation"><img src="https://agentmods.dev/badge/skills/nexus-substrate/nexus-agents/e2e-validation.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 | $0.00146 | $0.01509 |
| Opus 5 | $0.00073 | $0.00754 |
| Sonnet 5 | $0.00029 | $0.00302 |
| Haiku 4.5 | $0.00015 | $0.00151 |
Grade A, and why
e2e-validation 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 5d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End-to-End Validation Skill
Unit tests prove a function does what its test says. They do not prove the
real loops work: that the live voter panel actually returns 7 votes, that
run_dev_pipeline wires every stage, that routing picks a reachable adapter,
that the audit chain verifies. This skill runs the real loops with live
adapters and compares observed behavior against what the code, docs, and recent
"fixed" claims assert. Where reality diverges, it files a tracked issue.
Why this exists: this is dogfooding for validation, not implementation.
dogfooding-issuesimplements open issues;dev-pipelineruns one pipeline;system-reviewis a static health check. This skill is the periodic real-usage smoke test of the whole substrate.
When to run
- After every release (a published version is a claim that the loops work).
- Weekly, or once ≥3 behavior-affecting fixes have landed since the last run.
- On demand when a claim is in doubt (e.g., "the voter race is fixed").
Record the trigger in the report. One run per trigger is enough — don't loop it.
Preconditions (fail closed)
- Live adapter required. Confirm at least one real CLI/model adapter is
authenticated (
nexus-agents doctor). This skill validates real behavior — never useconsensus_vote { simulateVotes: true }(random output, #2319) or any simulate/mock path. If no live adapter is available, record every step asBLOCKEDand stop — do not fabricate a pass. - Cost awareness. Real loops spend tokens. If work is cost-gated, note it and
get authorization before the full run; a reduced run (e.g.
--quickvotes,dryRunpipelines) is an acceptable partial — label it as such. - Note the versions. Capture the installed
nexus-agentsversion and git SHA so the report is reproducible.
The loop — exercise every feature family
Pick one real, non-trivial seed task (a genuine backlog item works best, so the run produces real value). Drive it through the families below, capturing the actual tool output each step. Don't paraphrase success — paste/observe the real result and judge it.
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.
- 5d ago First seen · 109 lines · 146 tokens per session scan A bd0ed6269480
e2e-validation is a skill published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed yesterday), licensed MIT. It adds 146 tokens to every session and 1,509 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.