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 skills add ArabelaTso/Skills-4-SE --skill module-level-code-translatorgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/module-level-code-translator)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/module-level-code-translator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/module-level-code-translator/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/skills/arabelatso/skills-4-se/module-level-code-translator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/module-level-code-translator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00096 | $0.01506 |
| Opus 5 | $0.00048 | $0.00753 |
| Sonnet 5 | $0.00019 | $0.00301 |
| Haiku 4.5 | $0.00010 | $0.00151 |
Grade A, and why
module-level-code-translator 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 9d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module-Level Code Translator
Translate source code between programming languages while preserving behavior, adapting idioms, and generating verification tests.
Translation Workflow
Follow this sequential process for code translation:
1. Analyze Source Code
Before translating, thoroughly understand the source code:
- Identify scope: Determine if translating functions, classes, or entire modules
- Map dependencies: List all imports, external libraries, and dependencies
- Understand behavior: Identify core logic, algorithms, and expected behavior
- Note language-specific features: Identify features that require special handling (decorators, generators, async/await, etc.)
- Extract test cases: If existing tests are available, analyze them to understand expected behavior
2. Plan Translation Strategy
Create a translation plan before writing code:
- Map standard libraries: Identify equivalent libraries in target language (see references/stdlib_mappings.md)
- Adapt idioms: Plan how to translate language-specific patterns (see references/language_mappings.md)
- Handle type systems: Plan type annotations/declarations if moving between typed/untyped languages
- Identify testing framework: Choose appropriate testing framework for target language (see references/testing_frameworks.md)
- List transformations: Document major transformations needed (e.g., class → struct, decorator → annotation)
3. Translate Code
Implement the translation following target language conventions:
Core principles:
- Preserve original behavior exactly
- Follow target language idioms and conventions
- Maintain code structure when possible (functions → functions, classes → classes)
- Adapt patterns that don't translate directly (e.g., Python decorators → Java annotations)
- Add appropriate error handling for target language
- Include necessary imports and dependencies
Common transformations:
Python → JavaScript:
- Classes: Keep class structure, adapt
__init__toconstructor - List comprehensions: Convert to
.map(),.filter(),.reduce() - Decorators: Convert to higher-order functions or use libraries
- Type hints: Convert to TypeScript or JSDoc comments
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 198 lines · 96 tokens per session scan A 7257094b2bbe
module-level-code-translator is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,506 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
optimize-for-gpu
GPU-accelerates scientific Python on NVIDIA hardware and verifies that the result is correct and faster. Use for CUDA/GPU optimization; CPU-bound NumPy, SciPy, pandas, scikit-learn, NetworkX, scikit-image, vector-search, image-processing, graph, simulation, or file-I/O workloads; CuPy, cuDF, cuML, cuGraph, cuVS…
polars
High-performance DataFrame library for Python ETL, analytics, and pandas migration. Use for expression-based data manipulation with lazy query optimization, parallel execution, streaming out-of-core processing, Arrow interoperability, and optional GPU execution.
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
document
Generate @moduledoc/@doc for tested Elixir features; may update their README section or ADR. Not for docs lookup, documentation audits/reviews, or capturing standalone decisions.
041-planning-plan-mode
Use when creating or refining a structured Java implementation plan from trusted issue summaries, approved designs, ADRs, OpenSpec changes, existing plans, or a valid combination. The plan records its source artifacts and derivation direction and can remain the execution artifact without requiring OpenSpec. This…