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 quattro/jax-numerics-agent --skill project_engineeringgit clone --depth 1 https://github.com/quattro/jax-numerics-agentWrote 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/quattro/jax-numerics-agent/project_engineering)<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/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/quattro/jax-numerics-agent/project_engineering"><img src="https://agentmods.dev/badge/skills/quattro/jax-numerics-agent/project_engineering.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.03784 |
| Opus 5.5 | $0.00010 | $0.01514 |
| Sonnet 5.5 | $0.00005 | $0.00757 |
| Haiku 4.5 | $0.00002 | $0.00378 |
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 2mo 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 — 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.mdchecklists/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.pysnippets/pyproject_minimal.tomlsnippets/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.
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.
- 2mo ago First seen · 404 lines · 24 tokens per session scan A 167238fc1b7a
project-engineering is a skill published in the GitHub repository quattro/jax-numerics-agent (9 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 3,784 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
train-pose
Train/evaluate WiFi pose models honestly — camera-supervised (MediaPipe + CSI) and camera-free (WiFlow), always checked against the mean-pose baseline before any PCK is quoted.
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.
experiment-audit
A review step that checks whether an experiment's reported results are supported by real data and a sufficiently broad test.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.
i4h-catheter-navigation-smoke
Run CPU-only fluorosim smoke tests (imports, preprocessing, CLI parsers). Use when asked to smoke-test catheter navigation in CI or without a GPU.