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/prep)<a href="https://agentmods.dev/commands/suboss87/fdeops/prep"><img src="https://agentmods.dev/badge/commands/suboss87/fdeops/prep/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/prep"><img src="https://agentmods.dev/badge/commands/suboss87/fdeops/prep.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.00010 | $0.00273 |
| Opus 5.5 | $0.00004 | $0.00109 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
prep 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: prep for a meeting or readout.
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.
Take the meeting label from what they said - sponsor sync, steering committee, demo, etc.
Run fde prep "<label>" (fallback: npx --yes fdeops prep "<label>"). Use their exact label in quotes.
Present the output in plain language: who matters, what was promised, what shipped, open risks, suggested talking points. Lead with what they need to say, not file names.
Do not invent facts missing from .fde/. People, numbers, and quotes must come from the record or the repo they pointed at - else mark unknown - ask: <question>.
Offer one focused question only if a missing fact changes the prep.
Done when: the human has a spoken-ready prep from the record and knows what is still unknown.
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 4656b03c32ba
- 1mo ago Changed bf7f07a93b4c
- 1mo ago First seen · 22 lines · 10 tokens per session scan A 86fa5960cf56
prep is a command published in the GitHub repository suboss87/FDEOps (969 stars, last pushed 8d ago), licensed MIT. It adds 10 tokens to every session and 273 once invoked, about $0.0000 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
do-task
Do an ad-hoc, tactical task on a work item with NO PDLC process — no spec chain, no phase gates, no review chain. Work, ask follow-ups on the thread, continue until the requester says it is done.
checklist-sop
Turn a process into a clear checklist or standard operating procedure (SOP) anyone can follow without you.
prioritize-tasks
Prioritize a task list by importance and urgency (Eisenhower matrix) and turn it into a clear order of action.
design-notification-system
Design notifications with a frequency budget, the right channel per message, and real user control.
improve
Make any piece of work better, keeping its intent and voice while fixing the weaknesses. A quick /improve command.
meeting-notes
Chuyển transcript hoặc ghi chú họp thành quyết định, việc cần làm, owner, hạn, rủi ro và câu hỏi mở.