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 aakashdhar/vibe-skill --skill vibe-e2egit clone --depth 1 https://github.com/aakashdhar/vibe-skillWrote 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/aakashdhar/vibe-skill/vibe-e2e)<a href="https://agentmods.dev/skills/aakashdhar/vibe-skill/vibe-e2e"><img src="https://agentmods.dev/badge/skills/aakashdhar/vibe-skill/vibe-e2e/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/aakashdhar/vibe-skill/vibe-e2e"><img src="https://agentmods.dev/badge/skills/aakashdhar/vibe-skill/vibe-e2e.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.00163 | $0.05702 |
| Opus 5.5 | $0.00065 | $0.02281 |
| Sonnet 5.5 | $0.00033 | $0.01140 |
| Haiku 4.5 | $0.00016 | $0.00570 |
Grade A, and why
vibe-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 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.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · +21 lines 14d02608a692
- 1mo ago First seen · 678 lines · 163 tokens per session scan A b709742e5830
vibe-e2e is a skill published in the GitHub repository aakashdhar/vibe-skill (7 stars, last pushed 1mo ago), with no licence file. It adds 163 tokens to every session and 5,702 once invoked, about $0.0007 per session on Opus 5.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-31.
Other skills, from other repositories
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.
playwright-auth-state
Playwright workflows for authenticated browser state reuse through storageState and setup projects.
playwright-network-mocking
Playwright workflows for deterministic third-party responses using page.route().
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
vibe-verify
Exercise a running product against acceptance criteria and report evidence. Build success alone does not verify behavior.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.