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 briefing-an-agentgit 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/briefing-an-agent)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/briefing-an-agent"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/briefing-an-agent.svg" alt="Measured on agentmods" 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.00099 | $0.01690 |
| Opus 5 | $0.00049 | $0.00845 |
| Sonnet 5 | $0.00020 | $0.00338 |
| Haiku 4.5 | $0.00010 | $0.00169 |
Grade A, and why
briefing-an-agent 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 8d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefing an Agent
Overview
A context pack gives an agent or a reviewer the right focused information, and nothing extra. It states the role, the mode, the question to decide, the goal, the files affected, the evidence to produce, the approvals, the actions that are off limits, where the ideas came from, the most important next action, and the state of the work so far.
A good brief is how you supply competence and clarity so the agent can decide well rather than be micromanaged: name what good looks like, and state the decision rights — what it may decide at the edge and what it must escalate. Authority that outruns the clarity in the brief is the setup for a confident, wrong action.
Decision contract
- Claim checked: the agent can answer what it may do, what must stay true, what evidence it owes, and when to stop -- its power over files, commands, network, credentials, approvals, and release is bounded no wider than the brief's clarity, with the goal anchor and forbidden actions stated.
- Artifact observed: the change-record path, its mode, the assigned role, and
context-packs.md-> a context-pack with role, goal anchor, scoped files/commands, phase, authority bounds, stop conditions, and the next action. - Decision affected: block -- whether the briefed agent may start, and the authority bounds it may act within.
- Failure class: boundary-overreach (authority wider than the brief's clarity, or forbidden actions and allowed files unstated).
- Next action: bound the authority to the brief and state the forbidden actions; stop or escalate when credentials, production data, or release power appear.
When to Use
- An AI agent is about to edit files, run commands, call tools, or prepare release evidence, and needs its role, authority, and stop conditions stated before it starts.
- A reviewer needs a one-screen summary of a Standard change record before beginning the review.
- A long research or build thread has to be boiled down into the context needed to act.
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.
- 8d ago First seen · 112 lines · 99 tokens per session scan A 5309f4f45196
briefing-an-agent is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 1,690 once invoked, about $0.0005 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.
nopus-simplify
Rewrite the immediately preceding assistant response with clearer and more direct prose when the user invokes this skill.
thumbgate-guard
Turn the agent's most recent mistake into an enforced ThumbGate prevention rule (a PreToolUse block gate) so the same bad tool call is intercepted before it runs again, in this and every future session across Claude Code, Cursor, Codex, Gemini, Amp, and Cline. Captures the failure with the capturefeedback MCP tool…
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
search-lessons
Search promoted lessons for corrective actions, lifecycle state, linked rules, and linked gates.
release
Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.