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.
npx agentmods add commands/runnithan/claudex-setup/ticketgit clone --depth 1 https://github.com/runnithan/claudex-setupWhat 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 | $0.00019 | $0.00259 |
| Opus 5 | $0.00010 | $0.00130 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
ticket 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 yesterday.
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
Pick up the Jira ticket $ARGUMENTS and set up for development:
-
Fetch the ticket using
mcp__atlassian__getJiraIssuewith key$ARGUMENTS. Display the summary, description, type, and current status. -
Transition to In Progress: Call
mcp__atlassian__getTransitionsForJiraIssueto get available transitions, thenmcp__atlassian__transitionJiraIssueto move it to "In Progress". -
Create a feature branch: Generate a branch name as
{ticket-key}-{slugified-summary}(lowercase, hyphens, max 50 chars). Create it frommainusingmcp__github__create_branchwith ownerYOUR_ORG, repoYOUR_REPO. -
Checkout locally: Run
git fetch origin && git checkout {branch-name}. -
Report: Confirm the ticket is in progress, the branch exists, and you're checked out on it.
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.
- yesterday First seen · 18 lines · 19 tokens per session scan A f7fd7468de20
ticket is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 259 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-08-31.
Other commands, from other repositories
pull
Command "pull" from sangrokjung/claude-forge, covering /pull - git pull (quick), 1단계: 현재 상태 확인, 2단계: pull 실행, 3단계: 출력 and 성공 시.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
create-smoke-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
create_worktree
description: Create worktree and launch implementation session for a plan.
install
Install Pi Verifier Agent — prerequisites, deps, persona validation, and provider env.