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-buddy-project-readinggit 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-buddy-project-reading)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-buddy-project-reading"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-buddy-project-reading/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-buddy-project-reading"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-buddy-project-reading.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.00029 | $0.01635 |
| Opus 5 | $0.00015 | $0.00817 |
| Sonnet 5 | $0.00006 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
nw-buddy-project-reading 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Reading for the Buddy Agent
The buddy agent answers questions about a project by reading it, not by guessing. Every answer must be traceable to a specific file and line. This skill is the reading protocol.
Goals
- Understand the project's architecture, current state, and methodology enough to answer the user's question.
- Cite every claim (
path:line) so the user can verify. - Avoid reading more than necessary — tokens and time both cost.
- Never invent file contents, function names, or architecture claims.
Order of inspection (cheap first)
Read in this order. Stop as soon as you have enough context for the current question.
1. Project identity (always, <1s)
README.md— what is this project, for whom.CLAUDE.md(project root) — how Claude-based tools should behave here.pyproject.toml/package.json/Cargo.toml/ equivalent — language, dependencies, versions, scripts.VERSIONor the version field in the package manifest.
These four files tell you the project's name, language, purpose, and roughly how big it is. Skip nothing here.
2. Planning and state
BACKLOG.md— the single source of truth for planned work (in nWave projects).CHANGELOG.md— recent user-visible changes.git status— what's in flight right now.git log --oneline -20— recent direction of travel.
If the user's question is "what should I work on next" or "what did we just do", these four are usually the answer.
3. Architecture documentation
docs/architecture/architecture-design.md(or similar SSOT file).docs/adrs/— Architecture Decision Records.docs/feature/— feature specs with wave subdirectories.
The architecture doc is authoritative for design intent. If a claim in the architecture doc contradicts the code, the code is what runs — but the mismatch is itself a finding worth reporting.
4. Source layout
lsthe top-level dirs.ls src/(or the project's source root).- Read the main entry point (
main.py,index.ts,Main.fs, etc.).
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 · 130 lines · 29 tokens per session scan A aacb24988ca6
nw-buddy-project-reading is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 1,635 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…