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 skills add bmbouter/redhat-agents --skill process-interviewgit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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/skills/bmbouter/redhat-agents/process-interview)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/process-interview"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/process-interview/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/skills/bmbouter/redhat-agents/process-interview"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/process-interview.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.00025 | $0.01356 |
| Opus 5.5 | $0.00010 | $0.00542 |
| Sonnet 5.5 | $0.00005 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
process-interview 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Run this after /jira-setup and before using any Jira-connected agents. Re-run whenever the team's Jira process changes.
Instructions
Interview the user about their Jira project setup. Ask questions conversationally — don't dump all questions at once. Group them into natural topics and confirm understanding before moving on.
If the user says they have existing documentation about their workflow, ask them to point you to it. Read it and use it to pre-fill answers, then confirm the details with the user.
Topic 1: Project Basics
- What is your Jira project key? (e.g.,
MYPROJECT,ACME) - What is your Jira instance URL? (e.g.,
https://yourcompany.atlassian.net) - Does your project use components? If so, which component(s) should always be set?
- Do you have a board? What type — Kanban or Scrum?
- Link to the board? (optional)
- Link to the roadmap? (optional)
Topic 2: Issue Types and Hierarchy
- What issue types does your project use? (Epic, Story, Task, Bug, Sub-task, etc.)
- Are there any issue types you explicitly do NOT use?
- Are sub-issues used under epics? If so, what types? (Tasks, Stories, Bugs?)
- Are standalone issues (no parent epic) common or exceptional?
- Do you use Sub-tasks under Stories/Tasks, or is the hierarchy flat (Epic → Task/Bug)?
Topic 3: Workflow and Statuses
- What statuses does your project use? List them in lifecycle order.
- What is the typical issue lifecycle? (e.g., New → Refinement → In Progress → Closed)
- Are there any status-specific rules? (e.g., "Epics never go to Refinement")
- How does an issue get onto the board? (e.g., transition to a specific status?)
- What resolution values are used when closing? (Done, Won't Do, Duplicate, etc.)
Topic 4: Required and Default Fields
- Are there fields that should ALWAYS be set on every issue? (priority, component, labels, etc.)
- What is the default priority? What priority values are available?
- Do you use labels? Any that should always be applied?
- Are there custom fields that are important? (e.g., "Blocked" flag, "Target start/end" dates)
- If so, get the custom field IDs (e.g.,
customfield_10517)
- If so, get the custom field IDs (e.g.,
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.
- 1mo ago First seen · 172 lines · 25 tokens per session scan A c5947ffd5c67
process-interview is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,356 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…