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 skills/flyfission/nuclear-grade-context-engineering/checking-source-claimsnpx skills add FlyFission/nuclear-grade-context-engineering --skill checking-source-claimsgit 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/checking-source-claims)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/checking-source-claims"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/checking-source-claims.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.00065 | $0.00999 |
| Opus 5 | $0.00032 | $0.00500 |
| Sonnet 5 | $0.00013 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
checking-source-claims 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking Source Claims
Overview
"Source lineage" means showing where an idea came from. Honest lineage keeps public claims clean. It links an idea to a real public source. At the same time, it keeps the repo from sounding like it formally meets that source's rules.
Decision contract
- Claim checked: every cited source is public and in the source map or marked "public URL needed", and each reference reads as influence or idea lineage rather than compliance, certification, or formal assurance.
- Artifact observed: the changed public text against
source-map.md,source-to-concept-crosswalk.md, andcompliance-boundaries.md-> narrowed wording and updated source-map or crosswalk rows. - Decision affected: warn -- whether public/source wording is narrowed to honest influence or idea lineage rather than a compliance claim.
- Failure class: overstated-lineage (an unconfirmed source cited as direct lineage, or a compliance/approval claim outside a disclaimer).
- Next action: downgrade the source to "public URL needed" or reword to influence; wording affecting regulated, customer, or investor trust escalates.
When to Use
- A doc, template, skill, command, or change record cites a source family.
- New standards, frameworks, agencies, or assurance-sounding terms show up.
- A public claim might sound like compliance, certification, approval, or formal verification.
- A dependency, model, API, or vendor claim might get confused with proof from your own repo.
When Not to Use
- The change is private code with no method claim and no source claim.
- A source cannot be made public; use private, project-specific controls outside this public repo.
Inputs
- The changed public text.
docs/00-standards-foundation/source-map.md.docs/01-field-guide/source-to-concept-crosswalk.md.docs/00-standards-foundation/compliance-boundaries.md.
Process
- Find every cited source family and every assurance-sounding term.
- Confirm each direct source is public, can be linked, and is listed in the source map.
- Sort each reference: is it an influence, an analogy, evidence, a requirement, an authority, or a vendor claim?
- Downgrade any unconfirmed source to "supporting context" or mark it "public URL needed."
- Reword claims as influence, idea lineage, or workflow inspiration.
- Remove or negate any wording that implies compliance, approval, or formal assurance.
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.
- 3d ago First seen · 99 lines · 65 tokens per session scan A c1f34cb4f89a
checking-source-claims is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 24d ago), licensed MIT. It adds 65 tokens to every session and 999 once invoked, about $0.0003 per session on Opus 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
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.
doca-compress
Use this skill for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or decompress-lz4-block tasks on a docacompress context (the hardware supports DEFLATE both directions plus LZ4 decompress; LZ4 encode is NOT…
git-ai-search
Search and restore AI conversation context from git history.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, FK…