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/netdata/ai-viewer/project-quality-gatesnpx skills add netdata/ai-viewer --skill project-quality-gatesgit 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-quality-gates)<a href="https://agentmods.dev/skills/netdata/ai-viewer/project-quality-gates"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-quality-gates.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.00070 | $0.12056 |
| Opus 5 | $0.00035 | $0.06028 |
| Sonnet 5 | $0.00014 | $0.02411 |
| Haiku 4.5 | $0.00007 | $0.01206 |
Grade A, and why
project-quality-gates scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Do not use `bash <(curl -Ls https://coverage.codacy.com/get.sh) ...` in CI. How it starts
The opening of the file, as written. The whole thing — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Gates
Operating Rule
Every gate listed here runs in CI on every push — except the benchmark regression gate (scripts/check-bench.sh), which is a local/workstation gate (its baseline is not comparable to CI-runner hardware; CI runs the bench compile-smoke + the gate's hardware-independent self-test). The assistant runs them all locally before reporting work done. If a gate fails: fix the root cause. Never weaken a gate to make it pass. Lowering a threshold or marking a test skipped to land a PR is a contract breach.
nolint policy (two cases, both require a reason — never a bare //nolint):
- Deferred-fix suppression (the finding is real but fixing it now is out of scope): forbidden unless the active SOW justifies it AND the directive links the tracking issue/SOW —
//nolint:rule // <reason>; see SOW-XXXX. - Permanent-architectural suppression (the finding is a verified false-positive for a deliberate, durable pattern — e.g.
nilerron areturn nilthat intentionally lets a stricter downstream check win, or on poll-loop rotation-tolerance): allowed with a//nolint:rule // <reason>stating why the pattern is correct. No tracking link is required because there is nothing to fix later. The reason must be specific; "false positive" alone is not enough. Prefer a config-level exclusion (with a YAML rationale comment) when a whole file or rule class is involved. Bare/unexplained//nolintis always a contract breach.
When a new pattern emerges that warrants enforcement, add it here AND to .agents/sow/specs/quality-gates.md AND to CI in the same commit.
Gate Catalog
Go — Module Tidiness
go mod tidy
git diff --exit-code go.mod go.sum
Threshold: zero diffs. scripts/lint.sh mirrors the CI lint job and runs
this before formatter/linter/security checks. A stale module graph is a local
gate failure, not a CI-only surprise.
Go — Formatting
gofmt -l <tracked Go files> # zero unformatted tracked files expected
goimports -l <tracked Go files> # zero unformatted tracked files expected
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.
- 5d ago First seen · 567 lines · 70 tokens per session scan A 2bbca13588c7
project-quality-gates is a skill published in the GitHub repository netdata/ai-viewer (2 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 12,056 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
phoenix-observability
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.
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.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
monitoring-observability
Monitoring and observability patterns for Prometheus metrics, Grafana dashboards, Langfuse v4 LLM tracing (astype, scorecurrentspan, shouldexportspan, LangfuseMedia), and drift detection. Use when adding logging, metrics, distributed tracing, LLM cost tracking, or quality drift monitoring.