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-adapters/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-adapters)<a href="https://agentmods.dev/skills/netdata/ai-viewer/project-adapters"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-adapters/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-adapters"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-adapters.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.00039 | $0.01040 |
| Opus 5.5 | $0.00016 | $0.00416 |
| Sonnet 5.5 | $0.00008 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
project-adapters 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapters
Mental Model
An adapter is a sealed unit that converts one source format into the canonical event stream. It knows everything about its format and nothing about anything else. See .agents/sow/specs/adapter-contract.md.
Adding a New Adapter
-
Read the format authoritatively first. Open the upstream source mirror under
/opt/baddisk/monitoring/repos/ai/<tool>/and read its persistence code. Sample real files (sanitized) from the operator's environment. -
Write the spec first. Create
.agents/sow/specs/adapter-<name>.md. Required sections: source format, record shape, watch strategy, cursor design, mapping to canonical events, sub-agent linkage, known edge cases, references. The spec is the source of truth; the code follows. -
Create the package.
internal/adapters/<name>/adapter.go. Implement thecanonical.Adapterinterface. Keep the file under 400 lines; split helpers into sibling files. -
Commit sanitized fixtures.
testdata/<name>/<scenario>/. Scenarios are listed intesting-strategy.md. Runscripts/sanitize-fixture.shbefore committing. -
Write tests. Scan, Tail, cursor resume, error handling, idempotency. Use golden files.
-
Register the factory.
internal/adapters/registry.go:registry["myadapter"] = myadapter.Factory -
Add auto-discovery probe.
internal/ingest/discover.go: add a probe entry that detects the format's presence on disk. -
Update docs.
README.mdSource Formats table;docs/adding-an-adapter.mdif any new patterns emerged. -
Open or update a SOW. Use the external reviewer gates from
project-second-opinionson the adapter SOW's gap analysis, implementation plan, and implementation before closing the work.
Modifying an Existing Adapter
- Read the adapter's spec under
.agents/sow/specs/adapter-<name>.md. - Read recent commits to that adapter (
git log -p internal/adapters/<name>/). - Check existing fixtures for coverage of the case you're touching.
- Make the change.
- Update the spec in the same commit as the code.
- Run
go test ./internal/adapters/<name>/...with-race. - If the canonical mapping changed, refresh golden files with
-update-goldenand inspect the diff manually before committing.
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 · 76 lines · 39 tokens per session scan A 960c1879ef35
project-adapters is a skill published in the GitHub repository netdata/ai-viewer (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,040 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
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.
material-ui-nextjs
Integrates Material UI with Next.js App and Pages routers using @mui/material-nextjs, Emotion cache providers, next/font, CSS layers with Tailwind/CSS Modules, Link component prop patterns, CSS theme variables SSR notes, and App Router useSearchParams + Suspense. Use when setting up or debugging MUI in a Next.js app.
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
Use when instrumenting a service from the inside so an incident can be explained from telemetry alone — wiring OpenTelemetry logs, metrics and traces, standing up a Collector, exporting via OTLP, and defining telemetry-driven alerts. NOT outside-in uptime probes, on-call rotation, or who-gets-paged (that is…
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
cloud-native-ebpf-observability
Use this skill when the user says 'ebpf tracing', 'ebpf observability', 'bpftrace', 'trace syscalls', 'kprobe', 'tracepoint', 'uprobe', 'off-cpu profiling', 'continuous profiling ebpf', 'libbpf ringbuf', 'measure latency in kernel'. Builds kernel- and user-level observability with eBPF: bpftrace one-liners for…