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-specs-sync/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-specs-sync)<a href="https://agentmods.dev/skills/netdata/ai-viewer/project-specs-sync"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-specs-sync/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-specs-sync"><img src="https://agentmods.dev/badge/skills/netdata/ai-viewer/project-specs-sync.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.00036 | $0.01695 |
| Opus 5.5 | $0.00014 | $0.00678 |
| Sonnet 5.5 | $0.00007 | $0.00339 |
| Haiku 4.5 | $0.00004 | $0.00169 |
Grade A, and why
project-specs-sync 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specs Sync
Why
Specs under .agents/sow/specs/ are the assistant's durable memory of what ai-viewer does. The operator does not read specs. The assistant writes specs for itself — for the next session, the next compaction, the next reviewer. When code drifts from specs, the assistant is silently betraying future-self: future SOWs base plans on a spec that no longer matches reality.
Core Rule: Specs Lead
Specs change first, before tests, before code. This is the inverse of the common "document at the end" pattern. The reasoning: a spec that describes the target behavior turns into the executable contract — tests are written against the spec, code makes the tests pass against the spec. If the spec lags, the implementation has nothing to be judged against.
The order on any non-trivial change:
- Spec update lands first (in the SOW Pre-Implementation Gate's
Spec Deltassection, then in the actual spec file). - Failing tests are written against the new spec.
- Implementation makes the tests pass.
- All four (spec + tests + code + docs) ship in a single commit.
Drift between spec and code is a regression by definition.
When Specs Must Update
| Code change | Spec(s) to update |
|---|---|
| Adapter parsing change | adapter-<name>.md |
| Canonical event type change | canonical-events.md |
| SQLite schema change | data-model.md |
| REST endpoint change | rest-api.md |
| SSE event type change | sse-protocol.md |
| New UI route or page | ui-pages.md |
| Frontend state pattern change | frontend-architecture.md |
| Ingester behavior change | ingester.md |
| Server behavior change | presenter.md |
| New default value | wherever it's documented |
| Bind/port/path default change | deployment.md |
| Security-relevant change | security.md |
| New external dependency | the package's spec + AGENTS.md tech-stack table |
| Test strategy change | testing-strategy.md |
| Health/logging change | observability.md |
If the relevant spec doesn't exist: create it in the same commit. If multiple specs are affected: update all.
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 · 135 lines · 36 tokens per session scan A ea07ac038cb8
project-specs-sync is a skill published in the GitHub repository netdata/ai-viewer (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,695 once invoked, about $0.0001 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
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.
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.
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.
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…