trust

A command for diagnosing why a client or contact has gone quiet, separating a missing work step from a loss of trust.

In plain words
What is it for?
Use it to review a stalled client relationship, record what happened as green, amber, or red, and agree on the smallest next action or rescue plan.
Why use it?
It replaces guesswork with recent engagement records and a clearly marked contact signal, then identifies either a process fix or a trust-recovery step.

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

agentmods
npx agentmods add commands/suboss87/fdeops/trust
Clone the repo
git clone --depth 1 https://github.com/suboss87/FDEOps

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00279
Opus 5 $0.00006 $0.00139
Sonnet 5 $0.00003 $0.00056
Haiku 4.5 $0.00001 $0.00028

Measured yesterday against content hash 86bcaca022f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

trust 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 yesterday.

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.

.claude/commands/trust.md · 22 lines

What it actually says

Load @fde (skills/fde/SKILL.md). Situation: they went quiet.

If fde resume shows NO ENGAGEMENT: ask "What should we call this client?" once, then you run fde resume --init. Never tell the human to type the CLI.

Say: "Is this a process gap, or a trust problem?"

Run fde resume (fallback: npx --yes fdeops resume) for recent signal history and open threads.

Log the contact with fde log contact "<who and what happened>" --signal amber|red|green (fallback: npx --yes fdeops log contact "…" --signal …). Pick the signal from what they said - do not guess.

If this is a trust fire (ghosting, blocked access, sponsor disengaged): read references/rescue.md and follow it. If it is a process gap, name the missing step and the smallest unblock.

Playback the signal and next move. Confirm before any write to .fde/.

Done when: the contact is logged with a signal and you have a rescue or process next step the human agrees to.

Not for TypeScript errors, unit tests, refactors, or git commits - those stay in the host agent.

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. yesterday First seen · 22 lines · 13 tokens per session scan A 86bcaca022f7

Subscribe to this mod's changes

trust is a command published in the GitHub repository suboss87/FDEOps (213 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 279 once invoked, about $0.0001 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.