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/dmzoneill/redhat-ai-workflow/integration-testsgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWrote 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/dmzoneill/redhat-ai-workflow/integration-tests)<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/integration-tests"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/integration-tests.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.00000 | $0.00501 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
integration-tests 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/integration-tests
Review Konflux integration test status.
Overview
Review Konflux integration test status.
Underlying Skill: check_integration_tests
This command is a wrapper that calls the check_integration_tests skill. For detailed process information, see skills/check_integration_tests.md.
Arguments
| Argument | Required | Description |
|---|---|---|
application |
No | - |
Usage
Examples
skill_run("check_integration_tests", '{}')
# Check all integration tests
skill_run("check_integration_tests", '{}')
# Check specific application
skill_run("check_integration_tests", '{"application": "backend"}')
Process Flow
This command invokes the check_integration_tests skill. The process flow is:
flowchart LR
START([User runs /integration-tests]) --> VALIDATE[Validate Arguments]
VALIDATE --> CALL[Call check_integration_tests skill]
CALL --> EXECUTE[Execute Skill Steps]
EXECUTE --> RESULT[Return Result]
RESULT --> END([Complete])
style START fill:#6366f1,stroke:#4f46e5,color:#fff
style END fill:#10b981,stroke:#059669,color:#fff
style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
```text
For detailed step-by-step process, see the [check_integration_tests skill documentation](../skills/check_integration_tests.md).
## Details
## Instructions
```text
skill_run("check_integration_tests", '{}')
What It Does
- Lists integration test scenarios
- Shows recent test results
- Identifies failing tests
- Links to snapshot and pipeline details
Options
| Parameter | Description | Default |
|---|---|---|
namespace |
Konflux namespace | aap-aa-tenant |
application |
Application to check | All |
snapshot |
Specific snapshot to review | Latest |
Additional Examples
# Check all integration tests
skill_run("check_integration_tests", '{}')
# Check specific application
skill_run("check_integration_tests", '{"application": "backend"}')
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.
- 4d ago First seen · 91 lines · 0 tokens per session scan A 54e2c52af1c0
integration-tests is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 501 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 commands, from other repositories
migrate-nt-to-record
Convert the specified NamedTuple class to use @record from dagstershared.record.
validate_changed_docstrings
Validates Python docstrings in all uncommitted changed files using Sphinx parsing.
resume-work
Resume the current work session by loading active context from localdocs/.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
/opsx-archive
Archive a completed change in the experimental workflow.