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.
git clone --depth 1 https://github.com/suboss87/FDEOpsWrote 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/commands/suboss87/fdeops/trust)<a href="https://agentmods.dev/commands/suboss87/fdeops/trust"><img src="https://agentmods.dev/badge/commands/suboss87/fdeops/trust/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/suboss87/fdeops/trust"><img src="https://agentmods.dev/badge/commands/suboss87/fdeops/trust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00283 |
| Opus 5.5 | $0.00005 | $0.00113 |
| Sonnet 5.5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 1mo 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.
What it actually says
Load @fde (skills/fde/SKILL.md) and follow its Entry (every session) once. 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?"
Use the current entry packet for recent signal history and open threads; recall specific evidence when needed.
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.
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.
- 1mo ago Changed 957daf2009b7
- 1mo ago Changed dfce18b739cb
- 2mo ago First seen · 22 lines · 13 tokens per session scan A 86bcaca022f7
trust is a command published in the GitHub repository suboss87/FDEOps (946 stars, last pushed 10d ago), licensed MIT. It adds 13 tokens to every session and 283 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
implement.body
Every subagent invocation uses the delegation tool with the appropriate subagenttype (the implementation subagent, the tester subagent, or any specialized subagent the project ships). That tool is named Agent, in an interactive session and in the headless runtime alike. Do not look for a Task tool in your toolbox…
agent-build-feature
A strict brief that makes a coding agent implement a feature end to end, matching the codebase and verifying it works.
estimate-work
Estimate a task or project honestly, by decomposing it, surfacing unknowns, and giving a range not a false point.
bug-report-triage
Turn a vague bug report into a structured, actionable ticket with severity and next steps.
decline-politely
Say no clearly and kindly, to a request, invitation, or offer, without burning the relationship or over-explaining.