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/doc-syncer)<a href="https://agentmods.dev/agents/juliusz-cwiakalski/agentic-delivery-os/doc-syncer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/doc-syncer/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/doc-syncer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/doc-syncer.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.00015 | $0.01641 |
| Opus 5 | $0.00008 | $0.00821 |
| Sonnet 5 | $0.00003 | $0.00328 |
| Haiku 4.5 | $0.00002 | $0.00164 |
Grade A, and why
doc-syncer 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 10d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<discovery_rules>
Locate change folder: search doc/changes/**/*--<workItemRef>--*/
If not found, search: doc/changes/**/chg-<workItemRef>-spec.md
Spec file: chg-<workItemRef>-spec.md
Plan file: chg-<workItemRef>-plan.md
Test plan: chg-<workItemRef>-test-plan.md
Folder pattern: doc/changes/YYYY-MM/YYYY-MM-DD--<workItemRef>--<slug>/
</discovery_rules>
Scope to check:
- `doc/00-index.md`
- `doc/guides/**`
- `doc/overview/**`
- `doc/spec/**`
- `doc/contracts/**`
- `doc/domain/**`
- `doc/quality/**`
- `doc/ops/**`
- `doc/diagrams/**`
- `doc/decisions/**`
Treat missing documentation as a gap to fill, not as a follow-up. For any changed capability, contract, process, operation, domain concept, quality concern, guide, or diagram, either reconcile the existing doc or create the missing doc in-change.
Feature specs are one gap type: if a coherent, nameable capability warrants `doc/spec/features/feature-<slug>.md` and none exists, create it. Routine edits, one-off scripts, and bug fixes to already-specced areas normally reconcile existing docs rather than create a new feature spec.
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.
- 10d ago First seen · 117 lines · 15 tokens per session scan A 8b7f555bba0a
doc-syncer is an agent published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (37 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,641 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
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…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.