Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

fdeops Adversarial Testing Fieldbook

A hard-won playbook for adversarially testing the fdeops CLI's engagement resolution, registry, hooks and <private> redaction boundary inside a throwaway sandbox.

Dev & CodingAdvanced★ 217⑂ 30AI score 7/10Last updated: Aug 27, 2026

What it does

  • Documents how to break resolveEngagement() in bin/fde.js across all six fallback strategies (env var → registry bind → project CLAUDE.md → global pointer → folder-name match → in-repo .fde).
  • Enforces a sandbox harness (mktemp -d + FDEOPS_ENGAGEMENTS_ROOT) so no real engagement data is ever touched.
  • Requires decoy fixtures plus before/after sha256sum manifests, so "nothing else was written" is actually proven rather than assumed.
  • Gives concrete techniques for non-regular files (fifo/socket/dir/symlink) in memory slots: wrap every call in timeout 15 and preload an fs tracer to find the blocking call site.
  • Covers mutation-testing the recorded-session gate in bin/check.js, attacking the .registry parser, and proving <private> blocks never leak into any output surface.

Who it's for

  • Maintainers and contributors to the FDEOps repository.
  • QA/security engineers who want a model of rigorous adversarial CLI testing (path resolution, traversal, data isolation).
  • Node.js developers chasing intermittent hangs or silent misrouted writes.

Examples

  1. "Arm all five fallback strategies, set FDEOPS_ENGAGEMENT=client-zzz, and assert every read and write refuses without leaking another client's text."
  2. "Turn .registry into a symlink, fifo and directory in turn; confirm resume --init exits 1 with ENGAGEMENT READY, names the registry, and leaves no .registry.lock*."
  3. "Seed a <private> block into context.md/stakeholders.md/decisions.md and grep resume, triage, receipts and the dashboard HTML for the needle, using the on-disk files as the control."

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.agents/skills/testing-fieldbook/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .agents/skills/testing-fieldbook folder from the GitHub repo suboss87/FDEOps into my ~/.claude/skills/testing-fieldbook/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/suboss87/FDEOps.git && mkdir -p ~/.claude/skills && cp -r FDEOps/.agents/skills/testing-fieldbook ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal in your working directory.
  2. Clone the repository: git clone https://github.com/suboss87/FDEOps.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r FDEOps/.agents/skills/testing-fieldbook ~/.claude/skills/
  5. This skill only makes sense inside the FDEOps repo, so start Claude Code from the FDEOps directory.
  6. Verify Node.js with node -v and run npm install so npm run check works.
  7. Ask Claude: "Follow the testing-fieldbook skill and adversarially test engagement resolution."
View source on GitHub ↗License: MIT