Borrowing it
Nothing to install: this file belongs to paiml/depyler. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/paiml/depyler/main/.claude/commands/improve-compile-rate.mdgit clone --depth 1 https://github.com/paiml/depylerWrote 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/paiml/depyler/improve-compile-rate)<a href="https://agentmods.dev/commands/paiml/depyler/improve-compile-rate"><img src="https://agentmods.dev/badge/commands/paiml/depyler/improve-compile-rate.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.00578 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
improve-compile-rate 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Depyler Single-Shot Compile Rate: Autonomous Improvement Loop
Goal
Reach 80% single-shot compile rate on reprorusted-python-cli corpus. Work through bugs autonomously.
Measure First
cd /home/noah/src/reprorusted-python-cli
make corpus-retranspile
make corpus-e2e-rate
If >= 80%, report success and stop.
Iteration Loop
1. Find Top Error
cd /home/noah/src/reprorusted-python-cli
uv run python scripts/measure_compile_rate.py --json | jq -r '.failing[].error' | sort | uniq -c | sort -rn | head -5
2. Investigate
Find a failing example, read its Python source and generated Rust. Understand the gap.
3. Fix in depyler
Locations:
- Module mappings →
crates/depyler-core/src/direct_rules.rs - Type mappings →
crates/depyler-core/src/type_mapper.rs - Expr generation →
crates/depyler-core/src/rust_gen/expr_gen.rs - Cargo.toml →
crates/depyler-core/src/cargo_toml_gen.rs
4. Validate
cd /home/noah/src/depyler
cargo test -p depyler-core
cargo clippy -p depyler-core -- -D warnings
If fails: git checkout -- . and try different approach.
5. Measure Impact
cargo install --path crates/depyler --force
cd /home/noah/src/reprorusted-python-cli
make corpus-retranspile && make corpus-e2e-rate
If regression: rollback. If no change: still commit (may help other metrics).
6. Commit
git add -A && git commit -m "fix(core): [description] (Refs #193)"
7. Repeat until 80%
Bug Recovery
| Issue | Action |
|---|---|
| Tests fail | Rollback, try narrower fix |
| Regression | Rollback, add guards |
| Same error 3x | Skip, move to next pattern |
| Transpile drops | Rollback, fix is too broad |
Priority Errors (from corpus analysis)
cannot find value os- 16 filescannot find function date- 10 filesexpected value, found crate tempfile- 8 filesSCRIPT defined multiple times- 5 files
Exit
- SUCCESS: Rate >= 80%
- STUCK: No progress 5 iterations
- BLOCKED: Can't fix failing tests
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 · 74 lines · 0 tokens per session scan A c61192634bc1
improve-compile-rate is a command published in the GitHub repository paiml/depyler (358 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 578 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
cargo-metadata
Command "cargo-metadata" from olorehq/olore, covering cargo-metadata(1), name, synopsis, description and output format.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
cargo-build
Command "cargo-build" from olorehq/olore, covering cargo-build(1), name, synopsis, description and options.
cargo-check
Command "cargo-check" from olorehq/olore, covering cargo-check(1), name, synopsis, description and options.
cargo
Command "cargo" from olorehq/olore, covering cargo(1), name, synopsis, description and commands.
cargo-fetch
Command "cargo-fetch" from olorehq/olore, covering cargo-fetch(1), name, synopsis, description and options.