What is change-control-navigation?

A guide to an organization’s release-approval process, including required checks, evidence, deadlines, freeze periods, and who is allowed to perform each step.

Use it before work reaches production, especially when there is a change advisory board, formal stage gate, release calendar, freeze period, or separation between the person who writes and deploys a change.

It helps prevent technically finished work from missing a release window because approvals, notice periods, or role restrictions were discovered too late.

change-control-navigation — Skill for Claude Code by rpraharaj

Install

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.

Any agent

npx skills add rpraharaj/forward-deployed-engineer --skill change-control-navigation

Clone the repo

git clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineer

Made for: Claude Code.

Or install fde-core, the plugin that ships this one along with the rest of its 30 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/change-control-navigation.svg)](https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/change-control-navigation)

Your own site

<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/change-control-navigation"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/change-control-navigation.svg" alt="Measured on agentmods" height="20"></a>

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,051 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00102	$0.02051
Opus 5	$0.00051	$0.01026
Sonnet 5	$0.00020	$0.00410
Haiku 4.5	$0.00010	$0.00205

Measured 8d ago against content hash e3a84b15c47c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

change-control-navigation 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.

fde-core/skills/change-control-navigation/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The process between "it works" and "it's live."

Why this exists

In a large organization, technically complete and deployable are separated by a process: a change advisory board, a stage gate, a release calendar, a freeze window, mandatory lead times, and often segregation of duties meaning the person who wrote the change may not deploy it.

Engineers routinely treat this as bureaucracy to be endured at the end. That's the expensive reading. The process has lead times, and lead times only work if you start them early. A change completed on Monday that needs ten working days' notice for a fortnightly board doesn't ship this month.

An FDE is unusually exposed. You don't know this organization's process, it isn't written anywhere useful, and everyone around you has internalized it so thoroughly they won't think to mention it.

The good news: it's discoverable in about an hour, and knowing it early is close to free.

When this applies

Any engagement whose work will reach production
A CAB, stage gate, or formal approval exists
A release calendar or freeze period constrains the plan
Work is complete and can't ship
Planning — this belongs in delivery-plan, not after it

When it doesn't

Nothing reaching production this engagement
A mature continuous-delivery pipeline where the process is the pipeline. Confirm that's genuinely true rather than assuming it.
Executing an emergency change during an incident — follow the emergency path you already recorded; do not discover process under fire. Finding that path before you need it is part of this skill.

Prerequisites

.fde/00-engagement.md, and .fde/02b-ownership.md for who holds each gate.

Procedure

1. Find out what applies, by asking

This is not usually discoverable from the repository. It's a conversation, and it's a good early use of a knowledge-interview slot — or simply a direct question to a release manager or delivery lead.

This is usually a conversation. If no one is available, do not stall — reconstruct a first draft from the repo and tag it [inferred]:

Read the full file on GitHub · 188 lines

Changes

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 · 188 lines · 102 tokens per session scan A e3a84b15c47c

Subscribe to this mod's changes

change-control-navigation is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 21d ago), licensed MIT. It adds 102 tokens to every session and 2,051 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-31.