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 agents/konflux-ci/loadtest/issue-trackergit clone --depth 1 https://github.com/konflux-ci/loadtestWhat 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.00000 | $0.00167 |
| Opus 5 | $0.00000 | $0.00084 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
issue-tracker 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.
What it actually says
Issue tracker: Jira
Issues for this repo are tracked in Jira.
- Instance: redhat.atlassian.net
- Project: KONFLUX
- Component: Performance
Conventions
- Issues are managed via the Jira web UI or API or
acliCLI tool. - New issues should have the component set to "Performance".
When a skill says "publish to the issue tracker"
Create a Jira issue in the KONFLUX project with component "Performance". If CLI access is unavailable, present the issue title, description, and labels for the user to create manually.
When a skill says "fetch the relevant ticket"
Ask the user for the Jira issue key, or infer it from branch names / commit messages (e.g. KONFLUX-1234).
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 · 21 lines · 0 tokens per session scan A d51c5796da83
issue-tracker is an agent published in the GitHub repository konflux-ci/loadtest (2 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 167 tokens. 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 agents, from other repositories
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.