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/openshift-eng/ai-helpers/generate-feature-docgit clone --depth 1 https://github.com/openshift-eng/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/openshift-eng/ai-helpers/generate-feature-doc)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/generate-feature-doc"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/generate-feature-doc.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.00014 | $0.02214 |
| Opus 5 | $0.00007 | $0.01107 |
| Sonnet 5 | $0.00003 | $0.00443 |
| 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- generate-feature-doc — 92% identical, 8 lines differ
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
parent = KEYBFS - 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:
plugins/jira/skills/extract-prs/SKILL.mdplugins/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.
- 2d ago First seen · 258 lines · 14 tokens per session scan A 601171473008
generate-feature-doc is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 2,214 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.