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/oxy-hq/skillsWrote 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/oxy-hq/skills/eval-and-improve)<a href="https://agentmods.dev/commands/oxy-hq/skills/eval-and-improve"><img src="https://agentmods.dev/badge/commands/oxy-hq/skills/eval-and-improve.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.00035 | $0.02384 |
| Opus 5 | $0.00017 | $0.01192 |
| Sonnet 5 | $0.00007 | $0.00477 |
| Haiku 4.5 | $0.00003 | $0.00238 |
Grade B, and why
oxy:eval-and-improve scanned grade B with 2 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -rl '"name": "oxy-skills"' ~/.claude/plugins ~/.claude/projects ~/Documents 2>/dev/null \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://raw.githubusercontent.com/oxy-hq/oxy/refs/heads/main/json-schemas/agent.json How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval and Improve Oxy Skills
Evaluate all 4 oxy skills (or one specific skill) by running them against the current
project's real database, scoring the output against rubrics, and proposing targeted
improvements to each SKILL.md file.
Prerequisites Check
Before starting, verify:
-
You are in a copy of a real oxy project, not the live repo. Run
pwdand confirm this is a temp/eval directory, not production. -
Skill output directories are clean. The eval tests what each skill generates from scratch. Before starting, remove any pre-existing skill outputs so skills aren't judged on files they didn't create:
rm -f semantics/views/*.view.yml semantics/topics/*.topic.yml rm -f workflows/*.workflow.yml *.agent.yml *.app.ymlKeep:
config.yml,semantics.yml,example_sql/,globals/,.env -
Database schema is synced: Run
oxy syncifsemantics.ymlis missing or stale. -
oxy build requires a running PostgreSQL instance. Run
oxy start --enterprisein a separate terminal before starting this eval session.oxy start --enterpriselaunches a Docker PostgreSQL container and the oxy web server. It exposes PostgreSQL on port 15432 with default credentials. Add this to the project's.envso oxy can connect:OXY_DATABASE_URL=postgresql://postgres:postgres@localhost:15432/oxyNote:
oxy --version≥ 0.5.27 is only needed foroxy run --dry-runon SQL files, not foroxy build. -
Export OXY_DATABASE_URL at the start of this session. Each Bash tool call runs in a fresh shell, so
exportdoes not persist between calls. Read the value from.envonce and prepend it to everyoxycommand:export OXY_DATABASE_URL=$(grep OXY_DATABASE_URL .env | cut -d= -f2-)Then use this pattern for all oxy commands throughout the eval:
OXY_DATABASE_URL=$(grep OXY_DATABASE_URL .env | cut -d= -f2-) oxy build OXY_DATABASE_URL=$(grep OXY_DATABASE_URL .env | cut -d= -f2-) oxy run ...
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.
- 7d ago First seen · 240 lines · 35 tokens per session scan B 76edc3734b4c
oxy:eval-and-improve is a command published in the GitHub repository oxy-hq/skills (2 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 2,384 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.