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/dp-web4/SAGEWrote 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/dp-web4/sage/challenges)<a href="https://agentmods.dev/commands/dp-web4/sage/challenges"><img src="https://agentmods.dev/badge/commands/dp-web4/sage/challenges/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/dp-web4/sage/challenges"><img src="https://agentmods.dev/badge/commands/dp-web4/sage/challenges.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.00014 | $0.00667 |
| Opus 5.5 | $0.00006 | $0.00267 |
| Sonnet 5.5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
flow-nexus-challenges 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 First seen · 120 lines · 14 tokens per session scan A 5ab45467885d
flow-nexus-challenges is a command published in the GitHub repository dp-web4/SAGE (28 stars, last pushed today), licensed AGPL-3.0. It adds 14 tokens to every session and 667 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
ecc-guide
Navigate Multiversal's current agents, skills, commands, hooks, install profiles, and docs from the live repository surface.
evaluate
A command that evaluates mock interview answers using three debating agents. It reads a questionnaire and, when available, the candidate's resume and earlier evaluation files.
learn
Learn the GSD-Lite protocol — understand what it is, how it works in your project, and what you can do next.
bad-examples-block
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
kotlin-test
Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.
multi-workflow
Run a full multi-model development workflow with research, planning, execution, optimization, and review.