project-engineering

project-engineering is a skill for Claude Code, Codex from quattro/jax-numerics-agent. It costs 24 tokens per session (3,784 once invoked), scanned A, original, MIT.

Engineering guidance for JAX and Equinox projects, which are Python tools for numerical and machine-learning code. It covers stable APIs, documentation, continuous integration, testing, and data saving.

In plain words
What is it for?
Use it when designing, implementing, testing, documenting, or reviewing JAX/Equinox software.
Why use it?
It provides checklists and example snippets for making scientific code easier to maintain and verify.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/quattro/jax-numerics-agent/project_engineering
Any agent
npx skills add quattro/jax-numerics-agent --skill project_engineering
Clone the repo
git clone --depth 1 https://github.com/quattro/jax-numerics-agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for project-engineering

README.md
[![agentmods](https://agentmods.dev/badge/skills/quattro/jax-numerics-agent/project_engineering.svg)](https://agentmods.dev/skills/quattro/jax-numerics-agent/project_engineering)
Your own site
<a href="https://agentmods.dev/skills/quattro/jax-numerics-agent/project_engineering"><img src="https://agentmods.dev/badge/skills/quattro/jax-numerics-agent/project_engineering.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.03784
Opus 5 $0.00012 $0.01892
Sonnet 5 $0.00005 $0.00757
Haiku 4.5 $0.00002 $0.00378

Measured 5d ago against content hash 167238fc1b7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

project-engineering 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 5d 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.

skills/project_engineering/SKILL.md · 404 lines

How it starts

The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Engineering (JAX/Equinox Scientific Computing)

Guidance for software engineering practices around numerical/JAX codebases.

Companion checklists

Apply these checklists when using this skill.

Repo-local paths

  • checklists/project_engineering_checklist.md
  • checklists/testing_checklist.md

Global install paths (scripts/install_skills_with_assets.sh)

  • ~/.codex/skills/assets/checklists/project_engineering_checklist.md
  • ~/.codex/skills/assets/checklists/testing_checklist.md

Checklist workflow

  • Before implementation: open the relevant companion checklist(s) and scope the work against them.
  • During implementation: keep checklist items aligned with code/design decisions.
  • Before completion: re-run the checklist and explicitly document any intentionally unchecked item.

Companion snippets

Use these snippets as implementation starters when they match the task.

Repo-local paths

  • snippets/cli_skeleton.py
  • snippets/pyproject_minimal.toml
  • snippets/test_jvp_finite_difference.py

Global install paths (scripts/install_skills_with_assets.sh)

  • ~/.codex/skills/assets/snippets/cli_skeleton.py
  • ~/.codex/skills/assets/snippets/pyproject_minimal.toml
  • ~/.codex/skills/assets/snippets/test_jvp_finite_difference.py

Snippet workflow

  • Before implementation: start from the closest snippet and align it with repository conventions.
  • During implementation: keep public API shape, docs style, and error semantics consistent with this skill.
  • Before completion: remove placeholders and verify snippet-derived code is fully integrated.

Public API stability

Rule: Keep API structure stable and explicit

  • Do: Preserve return shapes/fields and document result codes/statuses.
  • Don’t: Change return structures or error semantics without deprecation.
  • Why: Scientific workflows rely on stable interfaces.
  • Example:
# Return a structured result: value + result + stats/state
return Solution(value=out, result=result, stats=stats, state=state)
  • Allowed break: Major version bump with migration guide.

Read the full file on GitHub · 404 lines

Changes

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.

  1. 5d ago First seen · 404 lines · 24 tokens per session scan A 167238fc1b7a

Subscribe to this mod's changes

project-engineering is a skill published in the GitHub repository quattro/jax-numerics-agent (9 stars, last pushed 22d ago), licensed MIT. It adds 24 tokens to every session and 3,784 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.

Related

Other skills, from other repositories

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

exploratory-data-analysis

Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

K-Dense-AI/scientific-agent-skills · 83 tokens

matlab

Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.

K-Dense-AI/scientific-agent-skills · 42 tokens

phylogenetics

Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.

K-Dense-AI/scientific-agent-skills · 68 tokens

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens