go

A front-door command that classifies a work request and sends it to the appropriate development process.

In plain words
What is it for?
Use it to route bugs to debugging, small fixes to direct implementation, and features through specification, planning, and building.
Why use it?
It prevents bugs, small fixes, and new features from being handled with the wrong level of planning or investigation.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/artttj/rapid-stack/go
Any agent
npx skills add artttj/rapid-stack --skill go
Clone the repo
git clone --depth 1 https://github.com/artttj/rapid-stack

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 341 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00038 $0.00341
Opus 5 $0.00019 $0.00170
Sonnet 5 $0.00008 $0.00068
Haiku 4.5 $0.00004 $0.00034

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

Security

Grade A, and why

go 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 2d 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/op/skills/go/SKILL.md · 31 lines

What it actually says

op:go

The front door. Classify, confirm, hand off — nothing is built here.

Classify

  • bug: existing behavior broken — an error, a wrong output, or a repro exists.
  • small fix: single surface, no new interface, roughly ≤2 files.
  • feature: new behavior or surface, or a multi-file change.

Ambiguous → resolve with an arrow-choice, not open text.

Confirm

Present the route as an arrow-choice before acting — bug → debug / small fix → direct build / feature → spec gate — with the classification first. One keypress fixes a misroute.

Route

  • bug → superpowers:systematic-debugging (absent → fallback: reproduce first, hypothesize from evidence, change one variable at a time, report root cause). Circling checkpoint: 3 disproven hypotheses or 20 minutes without new evidence → stop, restate what is known, fan out fresh-eyes subagents.
  • small fix → op:build direct mode.
  • feature → op:spec, which chains into op:plan and op:build, each behind its own gate.

Before a heavy route (feature gate, deep debug), suggest raising effort (xhigh/max) or an ultracode workflow; the user decides.

Proof at end: one line — the route taken and the first artifact produced (repro, test, or spec path).

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. 2d ago First seen · 31 lines · 38 tokens per session scan A c30ee338ee52

Subscribe to this mod's changes

go is a skill published in the GitHub repository artttj/rapid-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 341 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

autopilot

Full autonomous execution from idea to working code.

Yeachan-Heo/oh-my-claudecode · 12 tokens

statistical-power

Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…

xintaofei/codeg · 190 tokens

review-work

Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE…

code-yeongyu/oh-my-openagent · 125 tokens

chase-travel

Search Chase UR travel portal via Patchright for cash prices, points pricing, Points Boost offers, and Chase Edit hotel benefits. Use for pay-with-points portal comparison on Sapphire Reserve/Preferred.

borski/travel-hacking-toolkit · 44 tokens

points-valuations

Cents-per-point (cpp) valuations across major loyalty programs from four publications. Floor/ceiling rules for deciding if a redemption is good or exceptional.

borski/travel-hacking-toolkit · 35 tokens

awardwallet

Query AwardWallet for loyalty program balances, elite status, and transaction history. Use when checking points inventory, airline status, or planning trips on points.

borski/travel-hacking-toolkit · 33 tokens