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 skills add nWave-ai/nWave --skill nw-authoritative-sourcesgit clone --depth 1 https://github.com/nWave-ai/nWaveWrote 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/nwave-ai/nwave/nw-authoritative-sources)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-authoritative-sources"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-authoritative-sources/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/nwave-ai/nwave/nw-authoritative-sources"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-authoritative-sources.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01247 |
| Opus 5 | $0.00011 | $0.00624 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
nw-authoritative-sources 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 11d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
Domain Authority Database
Supplements general reputation tiers in source-verification with domain-specific authorities.
Software Architecture
| Source | Authority | Notes |
|---|---|---|
| martinfowler.com | Primary | Patterns, refactoring, enterprise architecture |
| c2.com/wiki | Historical | Original wiki; pattern language origins |
| microservices.io | Domain-specific | Chris Richardson's microservices patterns |
| architecturenotes.co | Curated | ADRs and trade-off analysis |
| infoq.com | Industry reporting | Conference talks, practitioner reports |
| thoughtworks.com/radar | Trend tracking | Technology Radar adoption lifecycle |
Cloud Platforms
| Source | Authority | Notes |
|---|---|---|
| docs.aws.amazon.com | Official | AWS, well-architected framework |
| cloud.google.com/docs | Official | GCP services and practices |
| learn.microsoft.com | Official | Azure, .NET, Microsoft ecosystem |
| kubernetes.io/docs | Official | Container orchestration |
| docs.docker.com | Official | Container runtime |
Security
| Source | Authority | Notes |
|---|---|---|
| owasp.org | Standards body | Web app security, top-10 |
| nist.gov | Government | NIST CSF, SP 800 series |
| cve.mitre.org | Vuln database | CVE identifiers |
| nvd.nist.gov | Vuln database | NVD with scoring |
| csrc.nist.gov | Crypto standards | FIPS, module validation |
| cisa.gov | Government advisory | Security advisories |
Standards Bodies
| Source | Authority | Notes |
|---|---|---|
| ietf.org / datatracker.ietf.org | Protocol standards | RFCs: networking, HTTP, TLS, DNS |
| w3.org | Web standards | HTML, CSS, WCAG, web APIs |
| iso.org | International | Quality, security, process frameworks |
| ecma-international.org | Language standards | ECMAScript spec |
| unicode.org | Character standards | Unicode encoding |
Programming Languages and Frameworks
| Source | Authority | Notes |
|---|---|---|
| docs.python.org | Official | Python, stdlib, PEPs |
| go.dev/doc | Official | Go language, stdlib |
| typescriptlang.org | Official | TypeScript handbook |
| rust-lang.org/learn | Official | Rust book, reference |
| developer.mozilla.org (MDN) | Canonical web ref | JS, HTML, CSS, Web APIs |
| docs.oracle.com/javase | Official | Java spec, API docs |
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.
- 11d ago First seen · 128 lines · 22 tokens per session scan A 7c93e458a194
nw-authoritative-sources is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 5d ago), licensed MIT. It adds 22 tokens to every session and 1,247 once invoked, about $0.0001 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-30.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
story-development
Implement user stories with test-driven development methodology.
implement
Use when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify. Enforces TDD: a failing test comes before the code that makes it pass, one task at a time, appended to a progress ledger that survives compaction. Delegates test tooling…