address

address is a command for Claude Code from synaptiai/synapti-marketplace. It costs 23 tokens per session (5,444 once invoked), scanned A, original, Apache-2.0.

A workflow for handling pull-request review feedback, which is the set of requested changes and comments from code reviewers. It categorises findings, applies focused fixes, and checks the result.

In plain words
What is it for?
Use it to resolve pull-request findings, verify the fixes, and request another review.
Why use it?
It helps turn review comments into tracked code changes while checking that fixes stay within scope and do not introduce new problems.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the flow plugin — 31 skills, 21 commands, 9 agents shipped together

Good fit Use it to resolve pull-request findings, verify the fixes, and request another review.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add synaptiai/synapti-marketplace
Claude Code
/plugin install flow

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 31 skills, 21 commands, 9 agents.

Wrote 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.

agentmods badge for address

README.md
[![agentmods](https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/address.svg)](https://agentmods.dev/commands/synaptiai/synapti-marketplace/address)
Your own site
<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>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,444 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash c20e2f24a028, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

plugins/flow/commands/address.md · 410 lines

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 phase
  • feedback-resolution — surgical changes, context recovery, pushback criteria
  • change-classification — verify no out-of-context changes
  • capability-discovery — quality commands for verification
  • tdd-patterns — test-first for fixes, test quality standards
  • holdout-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 resolution
  • references/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

Read the full file on GitHub · 410 lines

Changes

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.

  1. 5d ago First seen · 410 lines · 23 tokens per session scan A c20e2f24a028

Subscribe to this mod's changes

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.