fde-operate

A collection of practices for operating software after it has been delivered, focused on investigating data pipelines, watching deployments, and improving missing monitoring.

In plain words
What is it for?
Use it for pipeline investigations, post-deployment monitoring, and closing gaps in logs, metrics, or other operational checks.
Why use it?
It helps teams find operational problems after release and address places where the system does not provide enough visibility into failures or performance.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add rpraharaj/forward-deployed-engineer
agentmods
npx agentmods add plugins/rpraharaj/forward-deployed-engineer/fde-operate
Clone the repo
git clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineer

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 3 skills cost 316 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

fde-operate 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.

fde-operate/.claude-plugin/plugin.json · 7 lines

What it actually says

{
  "name": "fde-operate",
  "version": "0.1.0",
  "description": "FDE archetype pack for running what you shipped: pipeline forensics, post-deploy watch, and closing observability gaps.",
  "author": { "name": "FDE Portfolio" }
}
Contents

What it installs

The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 316 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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.

  1. 3d ago First seen · 7 lines scan A 8e18491e3d16

Subscribe to this mod's changes

fde-operate is a plugin published in the GitHub repository rpraharaj/forward-deployed-engineer (5 stars, last pushed 16d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Related

Other plugins, from other repositories