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/dryvist/claude-code-plugins/test-e2enpx skills add dryvist/claude-code-plugins --skill test-e2egit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/test-e2e)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/test-e2e"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/test-e2e.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.00017 | $0.00558 |
| Opus 5 | $0.00009 | $0.00279 |
| Sonnet 5 | $0.00003 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
test-e2e 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 2d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure End-to-End Test
Full pipeline validation across every infrastructure repo in dependency order. Validates syntax, plans changes, exports inventory, and dry-runs Ansible playbooks.
Pipeline Stages
Stage 1: OpenTofu Validate
In tofu-proxmox:
tofu validate
Stage 2: Terrakube Plan
In tofu-proxmox:
tofu plan
Stage 3: Export Inventory
Run /infra-sync-inventory to verify the RustFS artifact produced by the last
successful Terrakube apply.
Stage 4: Ansible Syntax Check
Run in parallel across all Ansible repos:
ansible-playbook --syntax-check -i inventory/hosts.yml playbooks/site.yml
Target repos: ansible-proxmox, ansible-proxmox-apps, ansible-splunk
Stage 5: Ansible Check Mode (Dry Run)
Run in parallel across all Ansible repos:
ansible-playbook --check -i inventory/hosts.yml playbooks/site.yml
Stage 6: Ansible Diff
Run in parallel across all Ansible repos:
ansible-playbook --check --diff -i inventory/hosts.yml playbooks/site.yml
Results
Report per-stage, per-repo pass/fail status:
| Stage | tofu-proxmox | ansible-proxmox | ansible-proxmox-apps | ansible-splunk |
|---|---|---|---|---|
| Validate | PASS/FAIL | - | - | - |
| Plan | PASS/FAIL | - | - | - |
| Syntax Check | - | PASS/FAIL | PASS/FAIL | PASS/FAIL |
| Check Mode | - | PASS/FAIL | PASS/FAIL | PASS/FAIL |
| Diff | - | PASS/FAIL | PASS/FAIL | PASS/FAIL |
Error Handling
Stage failures in OpenTofu block all subsequent stages. Ansible stage failures are independent per-repo.
Related Skills
- orchestrate-infra (infra-orchestration) — Master orchestrator for cross-repo infrastructure with dependency graph dispatch
- sync-inventory (infra-orchestration) — Export Terraform inventory and distribute to Ansible repositories
- infrastructure-standards (infra-standards) — Use when working on infrastructure repos (terraform, ansible, kubernetes, proxmox, nix devShells)
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.
- 2d ago First seen · 81 lines · 17 tokens per session scan A d42076a710fd
test-e2e is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 558 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
ci-pipeline-patterns
GitHub Actions workflow templates, matrix builds, caching, and monorepo CI strategies.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
pre-ship-review
Run a structured quality review before shipping code at any checkpoint such as PRs, releases, or milestones. Use whenever the user says.
backtesting-py-oracle
Configuration and anti-patterns for using backtesting.py to validate ClickHouse SQL sweep results. Ensures bit-atomic replicability between SQL and Python trade evaluation.