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/address)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/address"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/address.svg" alt="Measured on agentmods" 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.00023 | $0.05444 |
| Opus 5 | $0.00012 | $0.02722 |
| Sonnet 5 | $0.00005 | $0.01089 |
| Haiku 4.5 | $0.00002 | $0.00544 |
Grade A, and why
address 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 5d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address Review Feedback for PR #$ARGUMENTS
Systematic feedback resolution. Follows Explore > Plan > Code > Verify loop.
Required Skills
llm-operator-principles— foundational operator stance: convergence = zero findings, in-PR fixes by default, no calendar-time estimates, narrow escalation triggers. MUST be consulted before any other phasefeedback-resolution— surgical changes, context recovery, pushback criteriachange-classification— verify no out-of-context changescapability-discovery— quality commands for verificationtdd-patterns— test-first for fixes, test quality standardsholdout-validation— cross-reference self-review claims against file state (Phase 4)
References
references/escalation-format.md— canonical six-field structure used by Phase 3's out-of-scope-finding escalation, Phase 4's review-cycle-limit escalation, and any Proactive-Autonomy escalation surfaced during feedback resolutionreferences/finding-schema.md— canonical row shape every reviewer agent dispatched in the Phase 4 re-review fan-out emits
Phase 1: EXPLORE
gh pr checkout stays inline (mutating); read-only context-gathering is in the ! block below.
# Take the first whitespace-separated token; accept only if it is all digits.
# A non-numeric token (e.g., "foo42" or "evil;rm") is rejected with empty
# PR_NUM so it never reaches the prompt context or any downstream shell.
#
# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`. STATE=blocked on bad input.
_RAW="$ARGUMENTS" # Claude Code substitutes the bare arg token, not bash parameter-expansion
ARG1="${_RAW%% *}"
case "$ARG1" in
''|*[!0-9]*) PR_NUM="" ;;
*) PR_NUM="$ARG1" ;;
esac
echo "### PR Reference"
if [ -z "$PR_NUM" ]; then
echo "STATE=blocked"
echo "ERROR=PR number required (all-digit). Usage: /flow:address <pr-number>"
else
echo "STATE=ok"
echo "PR_NUM=$PR_NUM"
# Section: PR Details
echo ""
echo "### PR Details"
gh pr view "$PR_NUM" --json headRefName,baseRefName,title,body --jq '
"TITLE=\"\(.title)\"\nHEAD_BRANCH=\(.headRefName)\nBASE_BRANCH=\(.baseRefName)\nBODY_LENGTH=\(.body | length)"
' 2>/dev/null
# Section: Inline Review Comments
echo ""
echo "### Inline Review Comments"
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner' 2>/dev/null)
# Capture gh exit separately. gh failure ⇒ "" + non-zero exit; jq on empty
# stdin produces no output + exit 0, so `|| echo "0"` doesn't fire and the
# block silently emits a bare `INLINE_COUNT=` line. Distinguish unavailable
# (gh failed) from empty (gh ok, no records).
INLINE_JSON=$(gh api "repos/$REPO/pulls/$PR_NUM/comments" 2>/dev/null); GH_EXIT=$?
if [ $GH_EXIT -ne 0 ]; then
echo "INLINE_COUNT=0"
echo "STATE=unavailable"
INLINE_JSON="[]" # neutral fallback so the Conversation Threads section below also degrades gracefully
else
INLINE_COUNT=$(echo "$INLINE_JSON" | jq 'length' 2>/dev/null)
[ -z "$INLINE_COUNT" ] && INLINE_COUNT=0
echo "INLINE_COUNT=$INLINE_COUNT"
if [ "$INLINE_COUNT" = "0" ]; then
echo "STATE=empty"
else
# One record per comment; full body lives in the JSON cache for the agent
# to fetch on demand. The summary line carries the routing fields.
echo "$INLINE_JSON" | jq -r '.[] | "INLINE_COMMENT=id=\(.id) author=@\(.user.login) path=\(.path) line=\(.line // "?") length=\(.body | length)"' 2>/dev/null
fi
fi
# Section: Review Summaries
echo ""
echo "### Review Summaries"
REVIEWS_JSON=$(gh pr view "$PR_NUM" --json reviews --jq '.reviews' 2>/dev/null); GH_EXIT=$?
if [ $GH_EXIT -ne 0 ]; then
echo "REVIEW_COUNT=0"
echo "STATE=unavailable"
else
REVIEW_COUNT=$(echo "$REVIEWS_JSON" | jq 'length' 2>/dev/null)
[ -z "$REVIEW_COUNT" ] && REVIEW_COUNT=0
echo "REVIEW_COUNT=$REVIEW_COUNT"
if [ "$REVIEW_COUNT" = "0" ]; then
echo "STATE=empty"
else
echo "$REVIEWS_JSON" | jq -r '.[] | "REVIEW=state=\(.state) author=@\(.author.login) at=\(.submittedAt) length=\(.body | length)"' 2>/dev/null
fi
fi
# Section: Conversation Threads (grouped by file path)
echo ""
echo "### Conversation Threads"
THREADS=$(echo "$INLINE_JSON" | jq -r 'group_by(.path) | .[] | "THREAD=file=\(.[0].path) count=\(length)"' 2>/dev/null)
if [ -z "$THREADS" ]; then
echo "STATE=empty"
else
echo "$THREADS"
fi
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.
- 5d ago First seen · 410 lines · 23 tokens per session scan A c20e2f24a028
address is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 5,444 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.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Fetches the comment and diff via gh CLI, classifies it, applies the fix directly to the file if valid, posts a reply on the thread, and resolves it. Run from inside the repo.
done
Finish a task - document, create PR or merge, close.