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/plutosecurity/secure-flowWrote 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/plutosecurity/secure-flow/secure-flow-harden-dockerfile-fips)<a href="https://agentmods.dev/commands/plutosecurity/secure-flow/secure-flow-harden-dockerfile-fips"><img src="https://agentmods.dev/badge/commands/plutosecurity/secure-flow/secure-flow-harden-dockerfile-fips/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/plutosecurity/secure-flow/secure-flow-harden-dockerfile-fips"><img src="https://agentmods.dev/badge/commands/plutosecurity/secure-flow/secure-flow-harden-dockerfile-fips.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.00000 | $0.00577 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
secure-flow-harden-dockerfile-fips scanned grade A with 1 finding 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 9d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Transform your Docker images to FIPS compliant by removing root users and ensuring security best practices. Make all production docker images in this repository FIPS compliant by hardening Dockerfiles and ensuring they d Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 61 lines · 0 tokens per session scan A 64ff3ba9cba6
secure-flow-harden-dockerfile-fips is a command published in the GitHub repository plutosecurity/secure-flow (5 stars, last pushed 9mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 577 tokens. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
codex-loop
Claim the next dispatch:codex issue from the GitHub queue and work it end-to-end through codex exec: branch, implement, QA, PR. One invocation handles exactly one task — a local pull loop you trigger, not a daemon. The board/label safety model is identical to /loop; only the engine differs (the local Codex CLI instead…
loop
Claim the next dispatch:claude issue from the GitHub queue and work it end-to-end: branch, implement, QA, PR. One invocation handles exactly one task — this is a pull loop you trigger, not a daemon.
review
Review whatever you point it at — your working changes, a single PR, every open PR, the last N commits, or a time window — through the same review engine.
board
Inspect, configure, and reconcile the selected board through one provider-aware entry point. Preserve its existing workflow. The provider may be GitHub, Jira, or another connected system with clearly stated capability limits.
cleanup
Clean up what's already done. Default target is git hygiene: verify branches are provably merged into the trunk (squash-merge aware), then prune the merged local/remote branches and stale worktrees they leave behind. Explicit targets extend the sweep to completed GitHub issues and old session files.
design
Drive the full UI/design lifecycle from one command — run a technical quality audit, evaluate UX holistically, fix layout or copy, tone down an aggressive design, plan a feature before coding, or audit consistency across the app.