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/generate-feature-doc)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/generate-feature-doc"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-feature-doc/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/generate-feature-doc"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-feature-doc.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.00014 | $0.02208 |
| Opus 5 | $0.00007 | $0.01104 |
| Sonnet 5 | $0.00003 | $0.00442 |
| Haiku 4.5 | $0.00001 | $0.00221 |
Grade A, and why
generate-feature-doc 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
92% identical to generate-feature-doc — 8 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:generate-feature-doc
Synopsis
/jira:generate-feature-doc <feature-key>
Description
The jira:generate-feature-doc command generates comprehensive feature documentation by recursively analyzing a Jira feature ticket and all its related issues, sub-tasks, and linked GitHub pull requests.
This command is particularly useful for:
- Creating complete feature documentation after implementation
- Understanding the full scope and implementation details of a feature
- Generating onboarding materials for new team members
- Creating technical design documents from actual implementation
- Documenting complex features with multiple related issues and PRs
The command performs deep analysis of:
- The main feature issue and all related Jira tickets (recursively)
- All linked GitHub PRs, commits, and code changes
- Design decisions captured in PR discussions and code reviews
- Implementation details from actual code changes
Implementation
This command orchestrates two skills in sequence to generate comprehensive feature documentation:
-
Extract GitHub PRs (via
jira:extract-prsskill)- Discovers all descendant issues recursively using
childIssuesOf()JQL - Extracts PR URLs from Jira Remote Links (primary) and text content (backup)
- Fetches PR metadata from GitHub (state, title)
- Returns structured JSON with deduplicated PRs
- Discovers all descendant issues recursively using
-
Generate Documentation (via
jira-doc-generatorskill)- Receives PR data from step 1
- Analyzes MERGED PRs only (fetches metadata, diff, comments)
- Synthesizes feature documentation with the following sections:
- Overview
- Background and Goals
- Architecture and Design
- Usage Guide
- Related Resources (External Links only)
- Skip sections: Implementation Details, Testing
- Outputs to
.work/jira/feature-doc/<feature-key>/feature-doc.md
For detailed implementation, see:
extensions/jira/skills/extract-prs/SKILL.mdextensions/jira/skills/jira-doc-generator/SKILL.md
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 · 258 lines · 14 tokens per session scan A a830bf4ddc77
generate-feature-doc is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,208 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to generate-feature-doc, differing in 8 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).