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/.agents/skills/promote-issue/SKILL.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/skills/rshade/finfocus/promote-issue)<a href="https://agentmods.dev/skills/rshade/finfocus/promote-issue"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/promote-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/skills/rshade/finfocus/promote-issue"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/promote-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.00173 | $0.01816 |
| Opus 5.5 | $0.00069 | $0.00726 |
| Sonnet 5.5 | $0.00035 | $0.00363 |
| Haiku 4.5 | $0.00017 | $0.00182 |
Grade A, and why
promote-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 26d 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.
This is a copy
94% identical to pick-issue — 173 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promote Issue
Interactive selection of the next issue(s) to work, with optional promotion to
roadmap/current. This is the standalone promotion workflow extracted from the
/roadmap sync promotion gate — it does not rewrite ROADMAP.md wholesale or
sync labels repo-wide.
Preconditions
ghCLI authenticated forrshade/finfocus.- Repo root has
ROADMAP.mdandCONTEXT.md. If either is missing, skip every file-update step below and limit yourself to label flips — say so in the summary. The "Deliberately empty" escape hatch only writes ROADMAP.md, so it is unavailable in this case: do not offer it. - Read
CONTEXT.mdfirst. Any candidate that would cross a CONTEXT.md boundary must be flagged, not silently promoted.
Step 1 — Gather candidates
# Phase labels: roadmap/current | roadmap/next | roadmap/future (mutually exclusive)
gh issue list --state open --label roadmap/next --limit 1000 \
--json number,title,labels,body,milestone
gh issue list --state open --label roadmap/future --limit 1000 \
--json number,title,labels,body,milestone
# Cross-check what is already in flight; labels feed the composition_required score
gh issue list --state open --label roadmap/current --limit 1000 --json number,title,labels
If any query returns exactly its --limit of issues, the result may be
truncated. Rerun it with a higher limit; if it is still capped, report the
truncation in the summary and do not present the ranking as covering the whole
backlog.
Excluded from candidacy (never present them):
- Any label in the noise set:
nightly-failure,dependencies,agentic-workflows. roadmap/exclude— dominant; if it coexists with a phase label, report the conflict and leave it to the operator.- Already
roadmap/current(already in flight; listed only for WIP context). - More than one phase label (for example both
roadmap/nextandroadmap/future, so it appears in two queries). Report the conflict once and leave the issue out of ranking until the operator fixes its labels.
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.
- 26d ago First seen · 165 lines · 173 tokens per session scan A d999ba25ca76
promote-issue is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 173 tokens to every session and 1,816 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to pick-issue, differing in 173 lines, and is treated as a copy.
Other skills, from other repositories
notion-sync
Standardize Notion task updates across all modes.
phasing
Group slices into risk-optimized phases with timeline generation.
team-routing
Detect domain from context and find appropriate team member.
aws-cost-ops
AWS Cost Explorer — spending analysis, service breakdowns, forecasts, cost anomalies. Use when analyzing AWS spending, investigating cost spikes, reviewing network cost drivers like NAT Gateway, or forecasting next month's bill.
cis-aws-compute-2.4
Ensure an Organizational EC2 Tag Policy has been Created.
cis-aws-compute-2.3
Ensure Tag Policies are Enabled.