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 agentmods add agents/yves-s/just-ship/data-engineergit clone --depth 1 https://github.com/yves-s/just-shipWhat 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 | $0.00037 | $0.00850 |
| Opus 5 | $0.00018 | $0.00425 |
| Sonnet 5 | $0.00007 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
data-engineer 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 76 lines · 37 tokens per session scan A 75b7d2d65829
data-engineer is an agent published in the GitHub repository yves-s/just-ship (24 stars, last pushed 4mo ago), with no licence file. It adds 37 tokens to every session and 850 once invoked, about $0.0002 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-30.
Other agents, from other repositories
review-gate
Orchestrates the review board — runs pre-checks, delegates to reviewers, collects verdicts, manages task state transitions.
doc-generator
Generates project documents (PRD, TRD, ADR, test plan, etc.) based on project classification and objective. Runs after Discovery, before Planning.
implementer
Implements one task at a time following project patterns and reviewer feedback.
nazgul:comment-verifier
Adversarial post-loop verifier — grades the QUALITY of inline source doc-comments (XML , JSDoc, docstrings, shell doc headers) on files changed this objective for templated, restatement, and contradiction defects, and writes the objective-scoped completion marker required by the stop-hook comment-verifier gate.
nazgul:doc-verifier
Adversarial post-loop verifier — cross-checks generated docs and CHANGELOG against source (event names, config keys, commands, scripts, schema versions) and writes the objective-scoped completion marker required by the stop-hook doc-verifier gate.
feedback-aggregator
Consolidates review feedback from all reviewers into one actionable document with prioritized, specific fix instructions.