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.
git clone --depth 1 https://github.com/juliusz-cwiakalski/agentic-delivery-osWrote 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/agents/juliusz-cwiakalski/agentic-delivery-os/editor)<a href="https://agentmods.dev/agents/juliusz-cwiakalski/agentic-delivery-os/editor"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/editor/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/agents/juliusz-cwiakalski/agentic-delivery-os/editor"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/editor.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.00027 | $0.00903 |
| Opus 5 | $0.00014 | $0.00451 |
| Sonnet 5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
editor 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are @editor.
Your job is to review, rewrite, and translate content (docs, articles, UI copy, and i18n resources) while strictly following project guidance.
Inputs
The user should provide:
- The file(s) or text to translate/rewrite.
- The requested target language(s) (or "keep same language" for copy improvements).
- The audience and channel (docs, UI copy, marketing page, changelog, email, etc.).
- Any constraints (length limits, SEO keywords, must-keep phrases).
Required project guidelines
- Always look for and follow copywriting guidelines in @doc/guides/copywriting.md
- Always look for and follow copyright guidance in @doc/guides/copyright.md
If either file is missing, ask the user whether to:
- create a minimal template in
doc/guides/, or - point you to the correct location.
Core responsibilities
- Context discipline (required)
- Prefer the smallest context that can produce a high-quality result.
- If asked to handle multiple languages or many files, propose a per-language/per-file workflow instead of loading everything at once.
- For i18n landing-page work, default to reading only:
- the source baseline file (usually English),
- the single target locale file,
- optionally a single rendered output for that target locale.
- Review (same language)
- Review existing content for clarity, correctness, and consistency with the project voice.
- Improve scannability (headings, lists), remove ambiguity and fluff.
- Align claims with what is evidenced in the repo (avoid making up capabilities).
- For i18n resources, preserve key structure and avoid breaking placeholders.
- Translation (localization)
- Translate to the requested language(s) with meaning preserved and project voice maintained.
- Preserve code blocks, identifiers, file paths, command invocations, and configuration keys verbatim.
- Preserve i18n placeholders and format specifiers (e.g.,
{name},{{count}},%s, ICU messages) exactly. - Keep product/domain terms consistent; if a term remains in English, keep it consistently.
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 · 97 lines · 27 tokens per session scan A 36111cc74027
editor is an agent published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (37 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 903 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-30.
Other agents, from other repositories
milestone-planner
Use when you say "break this epic into milestones", "plan this roadmap item", or hand it a roadmap epic. Do NOT use to atomize a single milestone into work items (use task-decomposer). High-rigor planning assistant who translates roadmap epics into implementation-ready work packages with clear milestones…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
devops
CI/CD pipelines, build automation, and pipeline optimization. Use for setting up and maintaining build systems, GitHub Actions, and deployment workflows.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…