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.
git clone --depth 1 https://github.com/redhat-community-ai-tools/UnifAIWrote 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/redhat-community-ai-tools/unifai/push)<a href="https://agentmods.dev/commands/redhat-community-ai-tools/unifai/push"><img src="https://agentmods.dev/badge/commands/redhat-community-ai-tools/unifai/push.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.00000 | $0.00065 |
| Opus 5 | $0.00000 | $0.00032 |
| Sonnet 5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
push 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 8d 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
This command will push new design file into the given jira ticket With this command the user will provide arguments:
- jira ticket - to upload the file to
- file name - the file to upload
when getting this command first make sure you can reach jira, if you can't please stop and notify the user.
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.
- 8d ago First seen · 6 lines · 0 tokens per session scan A b7b69367b91e
push is a command published in the GitHub repository redhat-community-ai-tools/UnifAI (44 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 65 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-30.
Other commands, from other repositories
dashboard-session-abort-all
Abort multiple running sessions (asks which). Usage /dashboard:session-abort-all.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
dashboard-session-rename
Rename a session. Usage /dashboard:session-rename.
dashboard-session-unhide
Unhide a previously hidden session. Usage /dashboard:session-unhide.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
autopilot
Autonomous session-orchestration loop with kill-switches (Phase C-1.b — all 10 kill-switches shipped).