Borrowing it
Nothing to install: this file belongs to netdata/ai-viewer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/netdata/ai-viewer/master/.agents/skills/project-testing/SKILL.mdgit clone --depth 1 https://github.com/netdata/ai-viewerWrote 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/netdata/ai-viewer/project-testing)<a href="https://agentmods.dev/skills/netdata/ai-viewer/project-testing"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-testing/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/netdata/ai-viewer/project-testing"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-testing.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.00038 | $0.02190 |
| Opus 5.5 | $0.00015 | $0.00876 |
| Sonnet 5.5 | $0.00008 | $0.00438 |
| Haiku 4.5 | $0.00004 | $0.00219 |
Grade A, and why
project-testing 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Core Principle
Untested code is broken code. The operator does not manually test for the assistant. Every behavior the project ships has at least one automated test exercising it. Manual UI walkthroughs are diagnostics for the assistant; they are not proof of correctness. If a behavior cannot be tested, the design is wrong — refactor until it can be.
Tests are written before the implementation (see project-workflow). A failing test is the executable contract; the implementation makes it pass without weakening it.
Test Commands
# All Go tests (run during regular dev)
go test ./...
# With race detector (required in CI; also run before commits touching concurrency)
go test -race ./...
# One adapter
go test ./internal/adapters/aiagent_v3
# Update golden files for a single adapter
go test ./internal/adapters/aiagent_v3 -update-golden
# Coverage
go test -cover ./...
go test -coverprofile=coverage.out ./... && go tool cover -html=coverage.out
# Benchmarks
go test ./internal/adapters/... -bench=. -benchmem
# Frontend
cd frontend && npm test # vitest watch mode
cd frontend && npm test -- --run # one-shot
cd frontend && npm run e2e # playwright headless
AI_VIEWER_E2E_PORT=17710 npm run e2e # use a different local E2E port
cd frontend && npm run e2e -- --headed # playwright debug
cd frontend && npm run e2e -- --ui # playwright UI mode
# Full pre-commit check
./scripts/lint.sh && go test -race ./... && cd frontend && npm test -- --run && npm run lint
Test Pyramid
| Layer | Lives in | Run per |
|---|---|---|
| Adapter unit | internal/adapters/<name>/*_test.go |
every commit |
| Canonical/ingest/store unit | internal/*/ *_test.go |
every commit |
| Presenter handler | internal/presenter/*_test.go |
every commit |
| Go fuzz (parsers) | internal/adapters/<name>/{fuzz_test,*_fuzz_test}.go (canonical has no parser → no fuzz target) |
seed corpus per push (deterministic), 5min/target explore nightly |
| Go property-based (canonical mapping) | internal/canonical/property_test.go (rapid-go) |
every commit |
| Go E2E (ingest → store → server) | tests/e2e/*_test.go |
every commit |
| Performance benchmark | internal/adapters/aiagent_v2/bench_test.go, internal/adapters/claude_code/bench_test.go, internal/ingest/bench_test.go, internal/presenter/bench_test.go, internal/notify/bench_test.go |
local scripts/check-bench.sh (workstation gate; CI runs the compile-smoke), > 20% sec/op regression |
| Frontend component | frontend/src/**/*.test.tsx |
every commit |
| Frontend E2E (Playwright) | frontend/tests/*.spec.ts |
every commit |
| Frontend a11y (axe) | embedded in Playwright | every commit |
| Mutation testing (recommended) | internal/canonical/, internal/ingest/, adapters |
quarterly |
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 First seen · 179 lines · 38 tokens per session scan A 9027a15f3313
project-testing is a skill published in the GitHub repository netdata/ai-viewer (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 2,190 once invoked, about $0.0002 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
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
observability-phoenix
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
dd-unblock-pr
Load when investigating a failing PR CI pipeline or checking PR health. Attributes each CI failure as flaky, infra, or regression, proposes a targeted action, and reports code coverage.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.