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 agentmods add commands/flyfission/nuclear-grade-context-engineering/ng-report-defectgit 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/commands/flyfission/nuclear-grade-context-engineering/ng-report-defect)<a href="https://agentmods.dev/commands/flyfission/nuclear-grade-context-engineering/ng-report-defect"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-report-defect.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00693 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
ng-report-defect 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ng-report-defect
Portable command prompt generated from skills/reporting-shared-defects/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
Routes a defect found in a shared or supplied artifact (a shared prompt, skill, dependency, model, eval, or template) to the downstream teams, agents, and releases that depend on it, not just a local fix. Use when a discovered defect affects others who consume the same artifact. Do not use for a defect local to your own change, which is an ordinary fix, or for a live incident still being contained.
Use when
- 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.
Do not use when
- 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.
Inputs
- The defect, where it lives, and how it was found.
- The shared or supplied artifact and its consumers: teams, agents, releases, downstream repos.
- The severity, and how it could fail for a consumer who does not know about it.
- Any related incident, OPEX lesson, or deficiency entry, and the local fix already made.
Prompt text
Route a Nuclear-grade shared-defect report.
Inputs:
- defect and where it lives:
- shared or supplied artifact (prompt/skill/command/template/dependency/model/eval/config):
- consumers (teams, agents, releases, downstream repos):
- severity and how it fails for a consumer who does not know:
- local fix already made:
- related incident / OPEX / deficiency:
Return:
- a confirmation the defect lives in a shared or supplied artifact, not just your copy
- the downstream impact: who is affected and how
- the outward notice: to whom, what they need to do, the owner, and a tracking link
- the tie to the OPEX record and the deficiency register
- or, if it cannot reach others, the recorded reason no notice is needed
- escalation when security, credentials, data integrity, privacy, or a public release is touched
Treat the local fix and the outward notice as separate obligations. Do not imply formal assurance, compliance, or regulatory adequacy.
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.
- 5d ago First seen · 59 lines · 0 tokens per session scan A ebb7b7f406fc
ng-report-defect is a command published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 693 tokens. 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 commands, from other repositories
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
fix
Universal debugging and fix application with semantic code analysis.
status-enhanced
/forge:status-enhanced is the heavyweight sibling of /forge:status. While the standard status command gives you a quick overview, the enhanced version runs a full seven-source analysis: complete git history with a 7-day commit activity heatmap, full test suite execution with verbose output, TypeScript compilation…
domain-research
Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.