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/shakestzd/contextune/ctx-statusgit clone --depth 1 https://github.com/shakestzd/contextuneWrote 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/shakestzd/contextune/ctx-status)<a href="https://agentmods.dev/commands/shakestzd/contextune/ctx-status"><img src="https://agentmods.dev/badge/commands/shakestzd/contextune/ctx-status.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.01384 |
| Opus 5 | $0.00006 | $0.00692 |
| Sonnet 5 | $0.00002 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
ctx:status 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 4d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Status - Monitor Parallel Development
You are checking the status of all parallel worktrees and tasks.
Contextune Integration: This command can be triggered via /contextune:parallel:status or natural language like "check parallel progress", "show parallel status".
Execution Workflow
Step 1: Check for Active Worktrees
Run this command:
git worktree list
Expected output:
/Users/you/project abc1234 [main]
/Users/you/project/worktrees/task-0 def5678 [feature/task-0]
/Users/you/project/worktrees/task-1 ghi9012 [feature/task-1]
Parse the output:
- Line 1: Main worktree (skip)
- Lines 2+: Parallel worktrees (check each)
- Extract: worktree path, commit hash, branch name
If no worktrees found:
No parallel tasks active.
Stop here - nothing to report.
Step 2: Check Task Files for Status
For each worktree found, read its task file:
# Get task ID from worktree path
task_id=$(basename /path/to/worktrees/task-0)
# Read task status from YAML frontmatter
grep "^status:" .parallel/plans/tasks/${task_id}.md
Status values:
pending: Not started yetin_progress: Currently workingcompleted: Done and pushedblocked: Encountered error
Step 3: Check Git Status Per Worktree
For each worktree, check uncommitted changes:
cd worktrees/task-0
git status --short
cd ../..
Interpret output:
- Empty: Clean working tree (good!)
M file.ts: Modified files (work in progress)??file: Untracked files (needs git add)
Step 4: Check Branch Status (Ahead/Behind)
For each worktree, check if branch is pushed:
cd worktrees/task-0
git status --branch --porcelain | head -1
cd ../..
Example outputs:
## feature/task-0...origin/feature/task-0: Branch is up to date ✅## feature/task-0...origin/feature/task-0 [ahead 2]: 2 commits not pushed ⚠️## feature/task-0: No remote branch yet ⚠️
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.
- 4d ago First seen · 256 lines · 12 tokens per session scan A e3957877418a
ctx:status is a command published in the GitHub repository shakestzd/contextune (5 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 1,384 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
dedupe
You are a GitHub issue deduplication assistant. Your job is to determine if a given issue is a duplicate of an existing issue.
agent-router
전문 에이전트 자동 라우팅. 법률, 재무, 특허, SEO, 마케팅, 기획, BM 설계(BMC/Lean/JTBD/Wardley/Blue Ocean/Lightning Sprint), 코드리뷰, 아키텍처, 견적, CRM, HR/인사, 노무(노동법/해고/산재/취업규칙), 리서치, 데이터 분석, 제1원칙 사고, 주식 투자, 부동산 투자, 명리학, 회사운영(노란우산/창업혜택/고용지원/세무일정), 디자인 제작(배너/카드뉴스/SNS/광고/인포그래픽), FAQ/지식베이스(KCS/셀프서비스/아티클), 고객지원(CS응답/에스컬레이션) 등 50+ 에이전트.
compose-stack
Compose a sequenced Intelligence Stack Plan for a sovereign person. Analyzes their Genius Profile + Freedom Path + stated priorities + life stage, then sequences which of the 9 layers activate first, second, third. Produces a 90-day sprint plan for building their full intelligence stack. For humans with Genius Profile…
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
mach12:gh-issue-read
Read a GitHub issue's title, body, and all comments; optionally locate an HTML-marker comment.
mach12:gh-sub-issues
Detect sub-issues of a GitHub issue using the two-strategy approach (API, then body-parse).