Borrowing it
Nothing to install: this file belongs to rshade/finfocus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rshade/finfocus/main/.claude/commands/pick-issue.mdgit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/pick-issue)<a href="https://agentmods.dev/commands/rshade/finfocus/pick-issue"><img src="https://agentmods.dev/badge/commands/rshade/finfocus/pick-issue/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/rshade/finfocus/pick-issue"><img src="https://agentmods.dev/badge/commands/rshade/finfocus/pick-issue.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.03476 |
| Opus 5.5 | $0.00010 | $0.01390 |
| Sonnet 5.5 | $0.00005 | $0.00695 |
| Haiku 4.5 | $0.00002 | $0.00348 |
Grade A, and why
pick-issue 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Choose exactly one issue in rshade/finfocus, take it through implementation
and verification, and prepare a pull request. Stop after that issue. Adapted
from ax-go's pick-issue workflow for FinFocus's commands and repository rules.
An invocation to work an issue includes the claim and release comments below. A request only to recommend an issue, or to edit this workflow, does not. Respect the user's requested scope and existing authorization throughout.
Phase 0 — Preflight
Read AGENTS.md, CLAUDE.md, CONTEXT.md, and the constitution. Check for additional instructions in the directories you will touch.
ROOT="$(git rev-parse --show-toplevel)"
cd "$ROOT"
REPO=rshade/finfocus
gh auth status
git remote -v
git status --short
git worktree list
git fetch origin
Confirm origin points to FinFocus before using origin/main. Work in an
isolated worktree; preserve existing tracked and untracked changes in the
original checkout. Never stash someone else's work or stage files with
git add . or git add -A.
Phase 1 — Choose and claim
Inspect current work and candidates
gh label list --repo "$REPO" --limit 200 --json name,description
gh issue list --repo "$REPO" --state open --label roadmap/current --limit 100 \
--json number,title,body,labels,assignees
gh pr list --repo "$REPO" --state open --limit 100 \
--json number,title,headRefName,body
If a result reaches its limit, retrieve the remaining pages before concluding
that work is unclaimed. Check issues carrying processing:roadmap if that
label exists, and inspect their claim comments as described below.
FinFocus uses roadmap/current, roadmap/next, roadmap/future, and
effort/small, effort/medium, effort/large. Discover other labels at runtime.
There is no required area:* lane taxonomy: inspect issue bodies and relevant
files to identify overlap with active claims and open PRs. Pay particular
attention to shared engine types, CLI wiring, plugin protocols, go.mod,
go.sum, and shared fixtures. An absent lane label does not prove independence.
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 Changed · +53 lines 08ffe17d9c40
- 26d ago First seen · 263 lines · 24 tokens per session scan A 9e3a2cec8e96
pick-issue is a command published in the GitHub repository rshade/finfocus (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 24 tokens to every session and 3,476 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-09-29.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.