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-shared-artifact-trackinggit 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-shared-artifact-tracking)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-shared-artifact-tracking"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-shared-artifact-tracking/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-shared-artifact-tracking"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-shared-artifact-tracking.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.00034 | $0.00786 |
| Opus 5.5 | $0.00014 | $0.00314 |
| Sonnet 5.5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
nw-shared-artifact-tracking 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Artifact Tracking
Purpose
Shared artifacts are data values appearing in multiple places across a journey. Every ${variable} must have a single source of truth and documented consumers. Untracked artifacts are the primary cause of horizontal integration failures.
Artifact Registry Schema
shared_artifacts:
{artifact_name}:
source_of_truth: "{canonical file path}"
consumers: ["{list of places this value appears}"]
owner: "{responsible feature/component}"
integration_risk: "HIGH|MEDIUM|LOW - {explanation}"
validation: "{How to verify consistency}"
Common Artifact Patterns
Version
Source: pyproject.toml | Consumers: CLI --version, about command, README, install output
Risk: HIGH -- version mismatch breaks user trust
Install Path
Source: config/paths.yaml or constants.py | Consumers: install script, uninstall script, documentation
Risk: HIGH -- path mismatch breaks installation
Repository URL
Source: pyproject.toml or config | Consumers: README, error messages, install docs
Risk: MEDIUM -- URL mismatch breaks external links
Configuration Values
Source: config file or environment variable | Consumers: runtime behavior, documentation, defaults display Risk: MEDIUM -- inconsistency causes confusion
Command Names
Source: CLI argument parser definition | Consumers: help text, documentation, error messages, tutorials Risk: HIGH -- name mismatch makes features undiscoverable
Integration Validation
Consistency Check Process
- List all shared artifacts from journey schema
- For each artifact, verify source of truth exists
- For each consumer, verify it references correct source
- Flag any artifact without documented source
- Flag any consumer that hardcodes instead of referencing source
Validation Questions
- "Does every ${variable} in TUI mockups have a documented source?"
- "If the version changes, would all consumers automatically update?"
- "Are there hardcoded values that should reference a shared artifact?"
- "Do any two steps display the same data from different sources?"
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 · 84 lines · 34 tokens per session scan A b8d3e734d25a
nw-shared-artifact-tracking is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 786 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-09-06.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
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.
bo-risk-assessment
A method for assessing operational risks in a process, project, or supplier arrangement using observed facts, possible consequences, and practical response suggestions. It keeps the likelihood of a consequence conditional unless the evidence supports more.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
organize-task-files
Lists, pairs, deduplicates, and moves task files across the Coworker task state machine (0draft → 6git-pushed). Use when asked to organize, clean up, or audit task files.