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/suggest-improvementnpx skills add bmbouter/redhat-agents --skill suggest-improvementgit 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/suggest-improvement)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/suggest-improvement"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/suggest-improvement.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.1 | $0.00041 | $0.00634 |
| Opus 5 | $0.00020 | $0.00317 |
| Sonnet 5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
suggest-improvement 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Any agent should invoke this skill when it encounters:
- A skill that is missing information or gives bad guidance
- A workflow that could be improved based on real-world usage
- A gap — something the agent needed to do but had no skill for
- An error in an agent definition (wrong tool reference, missing prerequisite, etc.)
- A new pattern the user taught it that should be captured for everyone
Instructions
1. Classify the finding
Determine what type of improvement this is:
| Type | Label | Example |
|---|---|---|
| Bug in a skill | bug |
Skill says to use a JQL field that doesn't exist |
| Missing skill | enhancement |
Agent needed to do X but no skill exists |
| Skill improvement | enhancement |
Skill works but misses an important step |
| Agent definition issue | bug |
Agent lists a tool that isn't available |
| New pattern | enhancement |
User's workflow revealed a reusable technique |
| Documentation gap | documentation |
README is unclear or outdated |
2. Open a GitHub issue
Create a GitHub issue on bmbouter/redhat-agents:
Repository: bmbouter/redhat-agents
Issue title: [<asset-type>] <concise description>
- Example:
[skills] backlog-health-check: stale threshold should be configurable - Example:
[skills] process-interview: missing question about custom issue types - Example:
[agents] New agent needed: capacity planner
Issue body:
## What happened
[What the agent was doing when it found this]
## What's wrong / what's missing
[Specific problem or gap]
## Suggested fix
[How to improve it — be specific about what to change in which file]
## Files affected
- `<path to file>`
---
*Filed automatically by the [agent name] agent during a session.*
Labels: Apply the type label from Step 1.
3. Optionally create a PR
If the fix is straightforward and well-defined (e.g., adding a missing question, fixing a JQL query, updating a template), offer to:
- Create a branch:
improve/<short-description> - Make the change
- Open a PR against
mainreferencing the issue
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 · 81 lines · 41 tokens per session scan A 5ba66d205e01
suggest-improvement is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 634 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…