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/close)<a href="https://agentmods.dev/commands/suboss87/fdeops/close"><img src="https://agentmods.dev/badge/commands/suboss87/fdeops/close/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/close"><img src="https://agentmods.dev/badge/commands/suboss87/fdeops/close.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.00006 | $0.00175 |
| Opus 5.5 | $0.00002 | $0.00070 |
| Sonnet 5.5 | $0.00001 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
close 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. Stage: close.
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.
Read references/close.md and follow it. Handoff, receipts that survive you, what they operate.
Confirm before any write to .fde/. Do not invent a clean ending the record does not show.
Done when: handoff is on the record and the human agrees they are replaceable.
Not for a one-line typo in an unbound file. Bound client work, a POC, eval, or go-live stays on @fde.
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 f006f364d4af
- 1mo ago Changed f07e93cbf7b6
- 1mo ago Changed · -3 tokens per session b212efa31fa9
- 1mo ago First seen · 16 lines · 9 tokens per session scan A 2fca760604b5
close is a command published in the GitHub repository suboss87/FDEOps (970 stars, last pushed 10d ago), licensed MIT. It adds 6 tokens to every session and 175 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
contribute-to
Join an EXISTING, in-progress work item (issue or PR) as a contributor — walk the contribution loop toward a human-stated goal and success criteria, without the full spec chain.
finish-tasks
Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.
create-ticket
Create a work-item ticket (GitHub issue / Jira) from an existing requirements.md, then promote its draft spec folder to docs/specs/ /.
work-status
Report the current status of a work item by reading its spec files (requirements/design/tasks), its work-item state and the records under evidence/. Read-only.
estimate-work
Estimate a task or project honestly, by decomposing it, surfacing unknowns, and giving a range not a false point.
exec-one-pager
Write a one-page brief for executives that leads with the ask and the bottom line, backed by just enough evidence.