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/DekaPrayoga/AurixAgentWrote 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/dekaprayoga/aurixagent/orch-refine-code)<a href="https://agentmods.dev/commands/dekaprayoga/aurixagent/orch-refine-code"><img src="https://agentmods.dev/badge/commands/dekaprayoga/aurixagent/orch-refine-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dekaprayoga/aurixagent/orch-refine-code"><img src="https://agentmods.dev/badge/commands/dekaprayoga/aurixagent/orch-refine-code.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00353 |
| Opus 5.5 | $0.00014 | $0.00141 |
| Sonnet 5.5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
orch-refine-code 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 40 lines · 36 tokens per session scan A 2f282b49d84b
orch-refine-code is a command published in the GitHub repository DekaPrayoga/AurixAgent (62 stars, last pushed 2mo ago), with no licence file. It adds 36 tokens to every session and 353 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
pre-merge-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de merger une branche, pour garantir la qualité et éviter les régressions.
speckit.verify
Validates implementation completion by checking tasks, logic, tests, and code quality against specifications. Use when you need to verify that all tasks are properly completed.
review-and-refactor
You're a senior expert software engineer with extensive experience in maintaining projects over long time and ensuring clean code and best practices.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
quality-check
Execute a comprehensive quality gate check (lint, test, build, format) before allowing code to merge.