Borrowing it
Nothing to install: this file belongs to kimrejstrom/alpacalyzer-algo-trader. 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/kimrejstrom/alpacalyzer-algo-trader/main/.agents/commands/start-issue.mdgit clone --depth 1 https://github.com/kimrejstrom/alpacalyzer-algo-traderWrote 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/kimrejstrom/alpacalyzer-algo-trader/start-issue)<a href="https://agentmods.dev/commands/kimrejstrom/alpacalyzer-algo-trader/start-issue"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/start-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/kimrejstrom/alpacalyzer-algo-trader/start-issue"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/start-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.00000 | $0.00502 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
start-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 12d 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.
What it actually says
Start Issue Command
Start work on a GitHub issue.
Usage
/start-issue <issue_number>
Arguments:
issue_number: The GitHub issue number to work on
Argument Indexing
- Claude Code: Use
$1for the first argument (issue number) - OpenCode: Use
$ARGUMENTSto get all arguments
Steps
0. Preflight Check
Run issue-preflight.sh to validate the issue is ready:
bash scripts/issue-preflight.sh <issue_number>
If it exits non-zero, report the block reason from the JSON output and stop. Do NOT proceed with any further steps if preflight fails.
1. Get Repo Info
git remote get-url origin
Parse owner and repo name from the output.
2. Fetch Issue
Use gh CLI to fetch the issue:
gh issue view <issue_number> --repo <owner>/<repo>
3. Verify/Create Branch
Check current branch:
git branch --show-current
If not on correct branch, create one:
git checkout -b feature/issue-<issue_number>-<short-description>
Branch naming: feature/issue-{issue_number}-{short-description}
4. Create Plan File
Create docs/plans/_PLAN_issue-{issue_number}.md with:
# Plan: {issue_title}
## Issue
#{issue_number}
## Acceptance Criteria
- [ ]
## Tasks
- [ ]
## Notes
5. Scaffold Test File
Create test file in tests/:
tests/test_issue_{issue_number}.py
With basic test structure:
import pytest
def test_placeholder():
"""Placeholder test for issue #{issue_number}"""
assert True
6. Verify Tests Run
uv run pytest tests/test_issue_{issue_number}.py -v
7. Trigger code-review
Once done, call code-review sub-agent and enter in to a review - fix loop until review states PR is ready.
Notes
- This command is for starting NEW work on an issue
- If work is already in progress, skip this command
- Ensure you're on the correct branch before starting
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.
- 12d ago First seen · 117 lines · 0 tokens per session scan A 659ee956f1a8
start-issue is a command published in the GitHub repository kimrejstrom/alpacalyzer-algo-trader (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 502 tokens. 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-08-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.