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/oxy-hq/skills/testgit clone --depth 1 https://github.com/oxy-hq/skillsWhat 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.00011 | $0.00659 |
| Opus 5 | $0.00005 | $0.00329 |
| Sonnet 5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
oxy:test 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Oxy Agents and Workflows
Run evaluation tests defined in agent or workflow configuration files to validate reliability and output quality.
Pre-Test Steps
-
Check for Oxy installation
- Run
oxy --versionto verify Oxy CLI is installed - If not found, inform the user they need to install Oxy first
- Run
-
Determine test file
- If command invoked with argument (file path), use that file
- If no argument:
- Check if there's a currently open file in the editor
- If it's a
.agent.ymlor.workflow.ymlfile, use it - Otherwise, ask user to specify which file to test using AskUserQuestion
File Selection (if needed)
If no file specified:
- Search for test files using Glob:
**/*.agent.ymland**/*.workflow.yml - Use AskUserQuestion to let user select which file to test
- Options should show clear file paths
Test Execution
-
Run tests
- Execute
oxy test <file-path>with default options - Use pretty format for readable output
- Show test progress to user
- Execute
-
Monitor test execution
- Display each test case as it runs
- Show which assertions pass/fail
Results Summary
After tests complete, provide a clear summary:
If all tests pass:
✅ All tests passed!
File: <file-path>
Test cases: X passed, 0 failed
Accuracy: 100%
Your agent/workflow is ready to use.
If tests fail:
⚠️ Some tests failed
File: <file-path>
Test cases: X passed, Y failed
Accuracy: Z%
Failed tests:
1. [Test name]: [Reason for failure]
2. [Test name]: [Reason for failure]
Review the test configuration and agent/workflow logic.
Error Handling
Common issues:
- No tests defined: File has no
tests:section - inform user they need to add tests - File not found: Verify the file path is correct
- Invalid test format: Check test configuration syntax in the YAML file
- Execution error: Show the error and suggest checking agent/workflow configuration
Test Options
The command uses these defaults (recommended for most cases):
- Format: Pretty (human-readable)
- Threshold mode: Average (overall accuracy)
- Min accuracy: Not enforced (show results regardless)
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 · 102 lines · 11 tokens per session scan A 454b5ea444e4
oxy:test is a command published in the GitHub repository oxy-hq/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 659 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.