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.
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/status-rollup)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/status-rollup"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/status-rollup/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/wangke19/gemini-ai-helpers/status-rollup"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/status-rollup.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.00021 | $0.02161 |
| Opus 5 | $0.00010 | $0.01081 |
| Sonnet 5 | $0.00004 | $0.00432 |
| Haiku 4.5 | $0.00002 | $0.00216 |
Grade A, and why
status-rollup 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 5d 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
89% identical to status-rollup — 81 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:status-rollup
Synopsis
/jira:status-rollup issue-id [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]
Description
The jira:status-rollup command generates a comprehensive status rollup for any JIRA issue (Feature, Epic, Story, etc.) by recursively analyzing all child issues and their activity within a specified date range. The command intelligently extracts insights from changelogs and comments to create a concise, well-formatted status summary that can be reviewed and refined before being posted to Jira.
This command is particularly useful for:
- Weekly status updates on Features or Epics
- Sprint retrospectives and planning
- Executive summaries of complex work hierarchies
- Identifying blockers and risks across multiple issues
Key capabilities:
- Recursively traverses entire issue hierarchies (any depth) via
childIssuesOf()JQL - Analyzes status transitions, assignee changes, and priority shifts
- Extracts blockers, risks, and completion insights from comments
- Generates properly formatted Jira wiki markup with nested bullets
- Caches all data in a temp file for fast iterative refinement
- Allows review and modification before posting to Jira
This command uses the Status Analysis Engine skill for core analysis logic. See extensions/jira/skills/status-analysis/SKILL.md for detailed implementation.
IMPORTANT - Skill Loading Requirement:
Before processing any issues, you MUST invoke Skill(jira:status-analysis) to load the Status Analysis Engine skill. This ensures proper use of childIssuesOf() for hierarchy traversal and consistent analysis methodology. Do NOT rely on conversation summaries or memory - always load the skill explicitly at the start of execution.
Implementation
The command executes the following workflow:
0. Load Required Skills (MANDATORY)
This step is non-negotiable and must be performed first:
Skill(jira:status-analysis)
This loads the Status Analysis Engine skill which provides:
- Proper
childIssuesOf()usage for hierarchy traversal - Activity analysis methodology
- External links processing (GitHub PRs, GitLab MRs)
- Wiki comment formatting rules
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.
- 5d ago First seen · 237 lines · 21 tokens per session scan A 4a4378a8032e
status-rollup is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,161 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to status-rollup, differing in 81 lines, and is treated as a copy.
Other commands, from other repositories
projects
Provides tools for creating and managing your Supabase projects.
session-list
List recent sessions from the project ledger and offer to view one.
7a_stakeholder_comms
Generate stakeholder-facing communications: release notes, demo scripts, and change briefs.
convert-to-plan
Convert planning artifacts (lite-plan, workflow session, markdown) to issue solutions.
execute
Execute queue with DAG-based parallel orchestration (one commit per solution).
queue
Form execution queue from bound solutions using issue-queue-agent (solution-level).