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-second-opinionsnpx skills add netdata/ai-viewer --skill project-second-opinionsgit 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-second-opinions)<a href="https://agentmods.dev/skills/netdata/ai-viewer/project-second-opinions"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-second-opinions.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.1 | $0.00070 | $0.04530 |
| Opus 5 | $0.00035 | $0.02265 |
| Sonnet 5 | $0.00014 | $0.00906 |
| Haiku 4.5 | $0.00007 | $0.00453 |
Grade A, and why
project-second-opinions 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 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.
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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Opinions — Three Reviewer Gates
Non-Negotiable Open-Ended Review Rule
The only valid review is open-ended over the whole milestone/gate scope. Targeted class verification is necessary during claim verification, but it is not a substitute for a full open-ended review.
When external reviewers find any real P0/P1/P2 issue:
- Verify the exact claim.
- During verification, identify the issue class and count every occurrence of that class across the whole milestone scope.
- Then perform a fresh, unbiased, open-ended review of the entire milestone from scratch. Do not limit this review to the cited finding, the issue class, prior fixes, or prior reviewer rounds.
- Fix or reject every real issue from both the targeted verification and the open-ended review before rerunning external reviewers.
The common failure mode is biased limited review: a reviewer reports "X is wrong", the CTO checks only X-like issues, reruns reviewers, and reviewers then find unrelated Y/Z issues. That turns external reviewers into scouts. Stop and perform the whole-milestone open-ended review before any rerun.
External reviewers are a quality gate, not an implementation strategy. The CTO does the gap analysis, planning, coding, tests, gates, and self-review first. Reviewers then look for what was missed.
Minimal waste is part of correctness. One reviewer round runs six external models. A 19-round gate is roughly 114 model invocations before retries, timeouts, or failed outputs. That is not rigor; it means the CTO used reviewers as a discovery engine. That false framing is forbidden here. The CTO discovers, researches, writes, and self-reviews the stage artifact first; reviewers challenge that completed artifact.
The contract lives in AGENTS.md; this skill is the runtime pattern. If they
disagree, AGENTS.md wins.
Reviewer Set
Run these six reviewers for gate reviews:
| Reviewer | Invocation |
|---|---|
glm |
timeout 1800 opencode run -m "llm-netdata-cloud/glm-5.2-max" --variant max --agent code-reviewer "PROMPT" |
minimax |
timeout 1800 opencode run -m "llm-netdata-cloud/minimax-m3-coder" --variant max --agent code-reviewer "PROMPT" |
kimi |
timeout 1800 opencode run -m "llm-netdata-cloud/kimi-k2.7-code" --variant max --agent code-reviewer "PROMPT" |
mimo |
timeout 1800 opencode run -m "llm-netdata-cloud/mimo-v2.5-pro" --variant max --agent code-reviewer "PROMPT" |
deepseek |
timeout 1800 opencode run -m "llm-netdata-cloud/deepseek-v4-pro" --variant max --agent code-reviewer "PROMPT" |
qwen |
timeout 1800 opencode run -m "llm-netdata-cloud/qwen3.7-plus" --variant max --agent code-reviewer "PROMPT" |
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 · 471 lines · 70 tokens per session scan A 189bb4248762
project-second-opinions 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 4,530 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 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.