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 vetting-outside-code-and-modelsgit 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/vetting-outside-code-and-models)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/vetting-outside-code-and-models"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/vetting-outside-code-and-models/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/vetting-outside-code-and-models"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/vetting-outside-code-and-models.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.00085 | $0.01472 |
| Opus 5.5 | $0.00034 | $0.00589 |
| Sonnet 5.5 | $0.00017 | $0.00294 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
vetting-outside-code-and-models 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vetting Outside Code and Models
Overview
Trusting outside code is really a decision about how you will use it. A dependency, model, API, SaaS tool (software you rent online), or vendor claim should be accepted only for the job its evidence and controls actually support. Trust it for that job. Do not trust it past that.
Decision contract
- Claim checked: the dependency, model, API, or SaaS is accepted only for a use no broader than repo-side evidence supports, its critical characteristics independently verified by a named acceptance method, vendor claims kept apart from proof, each gap given a re-check trigger or routed to a release decision; a critical characteristic that cannot be independently verified blocks acceptance.
- Artifact observed: the named dependency/version/provider, vendor claims, and own-repo evidence -> a supplier-trust section or
supplier-trust.mdwith the use decision, gaps, backup controls, and release impact. - Decision affected: block -- whether to trust and use the dependency, model, API, or SaaS; unresolved gaps feed
ship.mddefer/block/ship-with-risk. - Failure class: boundary-overreach (trust stated past repo-side evidence, or vendor marketing treated as proof).
- Next action: route the unresolved gap to
ship.md; credentials, production data, or security/privacy claims escalate to a qualified review.
When to Use
- A change adds or updates a package, a model, an API, an online service, a generated file, a build service, or a data source.
- You are leaning on an outside claim as proof of behavior, security, privacy, reliability, licensing, or release readiness.
- A tool gets credentials, network access, data access, or a say in releases.
When Not to Use
- The dependency is for development only, easy to undo, and already covered by a quick proof.
- The request is only to cite a public source, not to lean on it as trust evidence.
- A qualified security or purchasing review is needed, which happens outside this repo.
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 · 103 lines · 85 tokens per session scan A ed67ea29c72b
vetting-outside-code-and-models is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 1,472 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
contextlock
Safely inspect a repository through the ContextLock MCP server. Use when exploring, searching, reviewing, or auditing repository files with ContextLock, especially before reading unfamiliar code or when sensitive files and secrets may be present.
parabricks
Plan NVIDIA Parabricks pbrun commands, translate CPU options and check runtime readiness. Use for individual tools, including planning-only questions.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
holoscan-install-wheel
Install Holoscan SDK 5.x CUDA 13 Python wheels in an isolated environment, choosing the full stack or version-matched components.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…