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 agents/iamcxa/kc-claude-plugins/e2e-scannergit clone --depth 1 https://github.com/iamcxa/kc-claude-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/agents/iamcxa/kc-claude-plugins/e2e-scanner)<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/e2e-scanner"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/e2e-scanner.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.00062 | $0.01104 |
| Opus 5 | $0.00031 | $0.00552 |
| Sonnet 5 | $0.00012 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
e2e-scanner 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Scanner
You scan E2E test reports, mappings, and flow definitions for improvement signals and return structured YAML output.
Input
You receive these fields from the orchestrator:
- plugin: target name (e.g.,
my-app) - plugin_path: absolute path to project root (e.g.,
~/Project/my-app) - repo: repository name (for signal routing)
- keywords: list of search terms relevant to the north star
- north_star: the target's qualitative north star goal
- proxy_signals: list of measurable proxy signal IDs and descriptions
Search Strategy (strict order)
Search ALL sources. Do not skip even if early sources return many results.
Source 1: E2E Test Reports (failure trends)
- Glob
{plugin_path}/e2e-reports/*/report.md— find all report files - Read the last 10 reports (sorted by directory name, which is timestamp-based)
- Look for: FAIL entries, step failures, assertion failures
- Track recurring failures: if the same step/flow fails in 3+ reports → high confidence signal
- If no
e2e-reports/directory exists, skip this source and note in output
Source 2: E2E Mappings (staleness check)
- Glob
{plugin_path}/.claude/e2e/mappings/*.yaml— find all mapping files - For each mapping:
Bash: stat -f "%m" {file}(macOS) to get last modification timestamp - Flag mappings older than 30 days as potentially stale
- If no mappings directory exists, skip and note
Source 3: E2E Flow Coverage (gap analysis)
- Glob
{plugin_path}/.claude/e2e/flows/*.yaml— inventory existing flows - Compare flow names against keywords to assess coverage
- Identify keyword topics that have NO corresponding flow (coverage gap)
- If no flows directory exists, this itself is a signal (no E2E coverage at all)
Confidence Rating
| Level | Criteria |
|---|---|
| high | Same test fails 3+ consecutive runs, mapping >60 days stale, critical keyword with zero flow coverage |
| medium | Test fails 2 runs, mapping >30 days stale, obvious coverage gap for secondary feature |
| low | Single failure, minor coverage gap, ancillary mapping staleness |
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.
- 3d ago First seen · 115 lines · 62 tokens per session scan A 4d631014c14b
e2e-scanner is an agent published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,104 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.