Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add synaptiai/synapti-marketplace/plugin install 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/synaptiai/synapti-marketplace/design)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/design"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/design/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/synaptiai/synapti-marketplace/design"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/design.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.00024 | $0.02496 |
| Opus 5 | $0.00012 | $0.01248 |
| Sonnet 5 | $0.00005 | $0.00499 |
| Haiku 4.5 | $0.00002 | $0.00250 |
Grade A, and why
design 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design: $ARGUMENTS
Architecture discussion and design validation. Follows Explore > Plan > Review > Decide loop.
Required Skills
This command operates with these domain skills loaded:
architecture-patterns— C4 design, coupling analysis, decision frameworkcapability-discovery— detect available agents and tech stackspecification-capture— read existing specification from journal or capture missing elements (Phase 1)
References
references/escalation-format.md— canonical six-field structure for any Proactive-Autonomy escalation surfaced during design
Phase 1: EXPLORE
Map existing architecture before proposing anything. Execute in parallel:
# Take the first whitespace-separated token; accept only if it is *all*
# digits. Inputs like "foo42 strategy" (greedy digit-extraction would pluck
# `42` and fire `gh issue view 42` on an unrelated issue) are rejected.
# Supports usage like /flow:design 42 (decoupled auth service architecture).
#
# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`.
_RAW="$ARGUMENTS" # Claude Code substitutes the bare arg token, not bash parameter-expansion
ARG1="${_RAW%% *}"
case "$ARG1" in
''|*[!0-9]*) ISSUE_NUM="" ;;
*) ISSUE_NUM="$ARG1" ;;
esac
echo "### Project Structure"
# Prefix each entry with ENTRY= per command-output-format.md (raw `ls -la`
# rows have no KEY= label). Each row contains whitespace (permission bits,
# owner, size, date, name), so values are double-quoted per rule 2.
# Try the conventional source roots first; fall back to repo root if none
# exist. Use `printf` so an empty ls produces a detectable empty var
# rather than a silent heading.
STRUCTURE=$(ls -la src/ app/ lib/ packages/ 2>/dev/null || ls -la 2>/dev/null)
if [ -z "$STRUCTURE" ]; then
echo "STATE=empty"
else
# Quote each row so values containing whitespace remain a single scalar
# under one KEY=. Embedded double-quotes (rare in ls output) are escaped
# with sed before wrapping.
printf '%s\n' "$STRUCTURE" | sed 's/"/\\"/g; s/^/ENTRY="/; s/$/"/'
fi
echo ""
echo "### Issue Reference"
# Quote parenthesized fallback per command-output-format.md rule 2.
echo "ISSUE_NUM=${ISSUE_NUM:-\"(none — exploratory design)\"}"
echo ""
echo "### Issue Context"
if [ -n "$ISSUE_NUM" ]; then
gh issue view "$ISSUE_NUM" --json title,body,labels --jq '"TITLE=\"\(.title)\"\nLABELS=\([.labels[].name] | join(","))\nBODY_LENGTH=\(.body | length)"' 2>/dev/null
echo ""
echo "#### Issue body"
gh issue view "$ISSUE_NUM" --json body --jq '.body' 2>/dev/null
else
echo "STATE=empty"
fi
echo ""
echo "### Branch Context"
echo "BRANCH=$(git branch --show-current 2>/dev/null)"
echo ""
echo "#### Recent commits"
RECENT_COMMITS=$(git log --oneline -5 2>/dev/null)
if [ -z "$RECENT_COMMITS" ]; then
echo "STATE=empty"
else
printf '%s\n' "$RECENT_COMMITS" | sed 's/^/COMMIT=/'
fi
true
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.
- 6d ago First seen · 255 lines · 24 tokens per session scan A 79ac24bbeee9
design is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,496 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
paper-trail-review
Review and arbitrate problematic references (cascade-exhausted, unresolved UID, awaiting OCR). Generates an up-to-date report, walks through cases by category, and applies arbitration decisions to the registry.
paper-trail-decide
Inspect a single reference in detail (identity, PDF status, acquisition history with verdicts, citation context in vault, state transitions) and decide its fate. Offers actionable decisions based on the ref's current state.
paper-trail-new-paper
Start writing an academic paper (IMRaD structure) on a topic, with anti-hallucination citation verification at every step. Builds on existing audited SOTAs.
paper-trail-registry-cleanup
Nettoyage historique du registre des fiches bibliographiques (les 900 fiches existantes). Cible les vieilles fiches mal nommées (0000, untitled) ET les duplicates avec suffixes numériques (foo2020bar2, 234) qui sont des artefacts de runs INGEST passés. Délègue les décisions au sub-agent textbook-resolver. Les merge…
paper-trail-linkify
Dernière passe du pipeline cible refondu. Insère les wikilinks finaux dans le SOTA (vers PDF si validé, sinon vers ancre dans une section ## Statut des sources régénérée idempotemment en bas du fichier). Présuppose que les passes identify/purge/acquire ont été lancées.