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 skills/bmbouter/redhat-agents/intake-triagenpx skills add bmbouter/redhat-agents --skill intake-triagegit 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/intake-triage)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/intake-triage"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/intake-triage.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.00036 | $0.00467 |
| Opus 5 | $0.00018 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
intake-triage 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.
What it actually says
When to Use
When a new ticket comes in, or when reviewing unrefined issues in the backlog.
Instructions
Read local/jira-workflow.md to understand issue types, required fields, and conventions.
1. Read the ticket
Get the full ticket details — summary, description, reporter, any comments or attachments.
2. Classify issue type
Apply the workflow config's decision rules:
- Is it broken behavior that was supposed to work? → Bug
- Is it a group of related work items? → Epic
- Is it a specific piece of work? → Task
- Apply any project-specific rules from the workflow config.
If the current type is wrong, recommend the correct type.
3. Search for duplicates
Search for issues with similar summaries or descriptions:
project = <PROJECT> AND summary ~ "<key terms>" ORDER BY created DESC
If potential duplicates exist, list them with similarity reasoning. Let the PO decide whether to close as duplicate.
4. Suggest field values
Based on the workflow config's required fields and defaults, suggest:
- Priority: Based on the description's urgency/impact language
- Component: Based on the area of the product affected
- Labels: Any that should always be applied
- Parent epic: Search for related epics and suggest the best fit
5. Present triage summary
## Triage: ISSUE-123
**Current**: Type=Task, Priority=unset, Component=none, Parent=none
**Recommended**:
- Type: Bug (description says "this used to work and now it doesn't")
- Priority: Major (affects user-facing functionality)
- Component: services
- Parent epic: EPIC-456 ("Authentication improvements")
- Duplicates: None found
**Missing fields**: acceptance criteria, description needs more detail
**Suggested next action**: Set fields and move to Refinement
Wait for PO approval before making any changes.
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 · 68 lines · 36 tokens per session scan A 5fc4baa3dada
intake-triage is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 467 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…