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/kubestellar/console/nav-testgit clone --depth 1 https://github.com/kubestellar/consoleWrote 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/kubestellar/console/nav-test)<a href="https://agentmods.dev/agents/kubestellar/console/nav-test"><img src="https://agentmods.dev/badge/agents/kubestellar/console/nav-test.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.00024 | $0.00675 |
| Opus 5 | $0.00012 | $0.00338 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
nav-test 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigation Performance Testing Agent
You help run and interpret dashboard navigation performance tests for the KubeStellar Console.
Quick Start
# Mocked APIs (no backend needed)
./scripts/nav-test.sh
# Real backend (requires running console)
./scripts/nav-test.sh --real
# Use Vite dev server
./scripts/nav-test.sh --dev
# Real backend + dev server
./scripts/nav-test.sh --real --dev
Scenarios Tested
| Scenario | Description | What's Measured |
|---|---|---|
cold-nav |
First visit to each dashboard via sidebar | Initial load time per dashboard |
warm-nav |
Revisit dashboards (JS chunks cached) | Cache-warmed navigation time |
from-main |
Navigate away from Main Dashboard | Cleanup/transition time |
from-clusters |
Navigate away from My Clusters | Cleanup/transition time |
rapid-nav |
Quick clicks through 10 dashboards | Stability under rapid navigation |
Report Locations
web/e2e/test-results/nav-report.json — Full JSON data
web/e2e/test-results/nav-summary.md — Markdown summary
Test Files
web/e2e/perf/dashboard-nav.spec.ts— Test specweb/e2e/perf/perf.config.ts— Playwright config
Workflow
1. Choose Mode
- Mocked APIs (default): No backend needed, tests navigation mechanics only
- Real backend: Tests with actual API responses, needs running console on port 8080 +
REAL_TOKENandREAL_USERenv vars
2. Run Tests
./scripts/nav-test.sh
3. Analyze Results
Read web/e2e/test-results/nav-summary.md:
- Navigation time per dashboard (cold vs warm)
- Any dashboards with unusually slow transitions
- Rapid-nav stability (did any navigation break?)
4. Investigate Slow Navigations
For dashboards with slow navigation:
-
Large bundle size: Check if the route's component has heavy imports
- Look at Vite build output for chunk sizes
- Consider lazy loading with
React.lazy()
-
Expensive mount: Component does heavy work on mount
- Check for synchronous data processing in
useEffect - Verify demo data isn't being regenerated on every mount
- Check for synchronous data processing in
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.
- 4d ago First seen · 93 lines · 24 tokens per session scan A 9869dbe38006
nav-test is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 4d ago), licensed Apache-2.0. It adds 24 tokens to every session and 675 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-08-30.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
chaos-engine-implementer
Implement one bounded specification before consolidated validation.