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 FlyFission/nuclear-grade-context-engineering --skill reporting-shared-defectsgit clone --depth 1 https://github.com/FlyFission/nuclear-grade-context-engineeringWrote 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/flyfission/nuclear-grade-context-engineering/reporting-shared-defects)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/reporting-shared-defects"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/reporting-shared-defects/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/flyfission/nuclear-grade-context-engineering/reporting-shared-defects"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/reporting-shared-defects.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.00093 | $0.01448 |
| Opus 5.5 | $0.00037 | $0.00579 |
| Sonnet 5.5 | $0.00019 | $0.00290 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
reporting-shared-defects 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting Shared Defects
Overview
A defect you find in something other people use is two problems, not one. The first is the bug itself, which you fix. The second is that every other consumer of that shared or supplied artifact still carries it and does not know. Fixing your own copy and moving on leaves them exposed. This skill makes the outward notice a first-class obligation alongside the local fix, so a defect in a shared prompt, skill, dependency, model, eval, or template reaches the teams, agents, and releases that depend on it.
Decision contract
- Claim checked: a defect found in a shared or supplied artifact has been evaluated for downstream impact and either notified to the affected consumers with an owner and a tracking link, or recorded as not-reportable with a reason -- never fixed locally and forgotten.
- Artifact observed: the defect, the shared or supplied artifact it lives in, and who consumes it -> a shared-defect report (description, affected consumers, severity, notice sent, owner, link) tied to the OPEX record and the deficiency register.
- Decision affected: block -- whether downstream consumers are notified (the local fix is not complete until they are), or the defect is recorded as not-reportable with a reason.
- Failure class: silent-local-fix (a defect in a shared artifact patched in one place while other consumers keep carrying it, unnotified).
- Next action: evaluate downstream impact and notify the affected consumers or owners; escalate when the defect touches security, data integrity, credentials, privacy, or a public release.
When to Use
- You found a defect in something others also use: a shared prompt, skill, command, template, dependency pin, model identifier, eval harness, or config.
- A fix you are about to make corrects your own copy but leaves other consumers exposed.
- An incident or OPEX lesson traced the cause to a shared or supplied artifact.
When Not to Use
- The defect is local to your own change and affects no other consumer; that is an ordinary fix.
- A live incident still needs containment first -- stabilize with
responding-to-incidents, then report. - The artifact has no other consumers, and none are foreseeable.
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 · 105 lines · 93 tokens per session scan A f46c7f1a6ff5
reporting-shared-defects is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It adds 93 tokens to every session and 1,448 once invoked, about $0.0004 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-30.
Other skills, from other repositories
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Remote or non-C++ control…
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime →…
compute-sanitizer-diagnose-cuda-bugs
Detect and diagnose CUDA correctness bugs with NVIDIA Compute Sanitizer. Routes GPU memory errors, shared-memory data races, uninitialized-memory reads, and synchronization/barrier bugs to the right sub-tool (memcheck, racecheck, initcheck, synccheck) and explains how to build, run, and read the report. Use when…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
doca-dpa-hl-tracer
Use this skill when the user runs docadpahltracer to capture/decode DPA-side traces at the programming-events layer (kernel entry/exit, sync points, comm primitive calls, RDMA WR submission, completion drain) — picking TRACE vs CRIT, tuning the JSON config (file-size limits + filesizelimitpolicy, thread…
holoscan-app-debug-build-run
Use when a concrete holoscan command in holoscan-applications or a standalone Module fails, hangs, regresses, or returns wrong output.