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 skills/neelprime/arbiterx/arbiterx-gatenpx skills add NeelPrime/arbiterx --skill arbiterx-gategit clone --depth 1 https://github.com/NeelPrime/arbiterxWrote 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/skills/neelprime/arbiterx/arbiterx-gate)<a href="https://agentmods.dev/skills/neelprime/arbiterx/arbiterx-gate"><img src="https://agentmods.dev/badge/skills/neelprime/arbiterx/arbiterx-gate.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.00020 | $0.00269 |
| Opus 5 | $0.00010 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
arbiterx-gate 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 6d 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
ArbiterX Gate
Run a quality gate on the last generated code or a specified file.
Instructions
Check for these categories:
Security (Critical — fails immediately)
- Hardcoded API keys (sk-..., AKIA..., ghp_..., xoxb-...)
- Hardcoded passwords in strings
- SQL injection (string formatting in queries)
- eval() or exec()
- subprocess with shell=True
Robustness (High priority)
- File operations without try/except or context managers
- Network calls without timeout parameter
- Bare except clauses (catch specific exceptions)
- Database operations without transaction handling
Efficiency (Medium priority)
- String concatenation in loops (use join())
- Nested loops over same collection (O(n²))
- re.compile() inside loops
- Unnecessary list() wrapping generators
Completeness (Must fix)
- TODO/FIXME/HACK comments
- Placeholder implementations
- Missing error messages in exceptions
Output Format
Score: XX/100
Status: PASS / FAIL
Issues:
1. [severity] file:line — description → suggested fix
2. ...
If FAIL: list exactly what to change to pass.
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.
- 6d ago First seen · 49 lines · 20 tokens per session scan A f42f027460e2
arbiterx-gate is a skill published in the GitHub repository NeelPrime/arbiterx (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 269 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
verify-language
Language-specific verification for Python, TypeScript/JavaScript, and Go. Checks type safety, language idioms, and best practices. Use when asked to "verify language", "check types", or for language-specific checks.
verify-quality
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".
quality
This skill should be used when the user asks about "code quality", "formatting", "linting", "lint rules", "code style", "error handling", "unsafe code", "documentation comments", "doc comments", "rustfmt", "prettier", "eslint", "clippy", or needs guidance on code quality enforcement and configuration.
pr-review
Use when conducting manual PR reviews - provides structured checklist covering security, performance, maintainability, and code quality dimensions with anti-sycophancy principles.
receiving-code-review
Use when receiving PR review feedback or code review comments. Enforces verification-first response to review feedback with anti-sycophancy classification and constructive disagreement protocol.