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 tracking-deficienciesgit 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/tracking-deficiencies)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/tracking-deficiencies"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/tracking-deficiencies/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/tracking-deficiencies"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/tracking-deficiencies.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.00080 | $0.01310 |
| Opus 5.5 | $0.00032 | $0.00524 |
| Sonnet 5.5 | $0.00016 | $0.00262 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
tracking-deficiencies 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracking Deficiencies
Overview
A deficiency you have decided to live with quietly becomes the new standard. This skill keeps a standing register of known problems so each one is aged, owned, and either fixed or formally accepted as risk with a named owner and a revisit date. The aim is to stop the slow normalization of deviation — the small erosions that, uncorrected, become the culture.
Decision contract
- Claim checked: every tracked deficiency has a visible first-seen age, a named owner, and a disposition -- a fix-by date or a formal risk-acceptance with a named owner and a concrete revisit trigger -- never "known, untracked."
- Artifact observed: the deficiency, where it shows up, its consequence and frequency, and any related incident/OPEX/controlled item -> a deficiency entry or
deficiency.mdrow (description, age, owner, disposition, review trigger) linked to those records. - Decision affected: block -- per deficiency, fix by a date or formally risk-accept it with a named owner and a revisit date.
- Failure class: normalized-deviation (a known problem living in chat/memory, or an accepted risk with no owner, date, or trigger).
- Next action: assign an owner and a fix-or-accept disposition; escalate when it touches safety, security, data integrity, or drives repeat incidents.
When to Use
- A known problem will outlive the current change: a flaky test, a noisy alert, an unowned service, a dead dashboard, a recurring incident, or deferred hardening.
- A review or incident surfaced something real that is not being fixed right now.
- You want to convert "we all know about that" into an owned, dated, decided entry.
When Not to Use
- A lesson is already fully closed inside a packet and needs no standing tracking.
- The work is brand-new and has no accepted deficiency yet (rate it as a normal change instead).
- The item is an active incident needing response, not logging (use
responding-to-incidents).
Inputs
- The deficiency, where it shows up, and how it was found.
- Its consequence and how often it bites.
- Who could own it, and whether a fix or a formal risk-acceptance is the right disposition.
- Any related incident, OPEX lesson, or controlled item.
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 · 107 lines · 80 tokens per session scan A 5fc87882f22e
tracking-deficiencies is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 1,310 once invoked, about $0.0003 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
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
task-decomposer
Produces phased task boards from feature requests: dependency-mapped work items, parallelization flags, risk flags, edge cases, test matrices. Triggers on: "decompose this feature", "task breakdown with dependencies", "phased implementation plan", "work breakdown structure". NOT for discovering which decisions are…
project-context-setup
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…
implementation-task-spec
Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering.
analiz-human-review-gate
Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analizreview column.
board-column-flow
Use when moving tasks or reporting status - the kanban column semantics, which columns are human/architect/QA gates, and where the PM actually acts.