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/appinterface-checkgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWhat 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.00543 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
appinterface-check 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/appinterface-check
Validate app-interface GitOps configuration.
Overview
Validate app-interface GitOps configuration.
Underlying Skill: appinterface_check
This command is a wrapper that calls the appinterface_check skill. For detailed process information, see skills/appinterface_check.md.
Arguments
| Argument | Required | Description |
|---|---|---|
saas_file |
No | - |
Usage
Examples
skill_run("appinterface_check", '{"saas_file": "$SAAS_FILE"}')
# Check tower-analytics SaaS
skill_run("appinterface_check", '{"saas_file": "tower-analytics"}')
# Check specific environment
skill_run("appinterface_check", '{"saas_file": "tower-analytics", "environment": "stage"}')
Process Flow
This command invokes the appinterface_check skill. The process flow is:
flowchart LR
START([User runs /appinterface-check]) --> VALIDATE[Validate Arguments]
VALIDATE --> CALL[Call appinterface_check 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 [appinterface_check skill documentation](../skills/appinterface_check.md).
## Details
## Instructions
```text
skill_run("appinterface_check", '{"saas_file": "$SAAS_FILE"}')
What It Does
- Validates app-interface configuration
- Shows SaaS file contents and refs
- Compares against live state
- Lists resource quotas and limits
Options
| Parameter | Description | Default |
|---|---|---|
saas_file |
SaaS file to check | Auto-detect |
environment |
Environment to validate | All |
Additional Examples
# Check tower-analytics SaaS
skill_run("appinterface_check", '{"saas_file": "tower-analytics"}')
# Check specific environment
skill_run("appinterface_check", '{"saas_file": "tower-analytics", "environment": "stage"}')
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 · 90 lines · 0 tokens per session scan A b54aede0c64f
appinterface-check is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 543 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
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
triage
Triage Linear issue with comprehensive analysis.