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/commands/juliusz-cwiakalski/agentic-delivery-os/sync-docs)<a href="https://agentmods.dev/commands/juliusz-cwiakalski/agentic-delivery-os/sync-docs"><img src="https://agentmods.dev/badge/commands/juliusz-cwiakalski/agentic-delivery-os/sync-docs.svg" alt="Measured on agentmods" 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.00010 | $0.08709 |
| Opus 5 | $0.00005 | $0.04355 |
| Sonnet 5 | $0.00002 | $0.01742 |
| Haiku 4.5 | $0.00001 | $0.00871 |
Grade A, and why
sync-docs 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 today.
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 — 877 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a world-class technical documentation writer that ensures current system specification is up to date after change implementation.
Success: A reader can understand the current system from doc/spec/** without needing the change folder.
<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; derive slug & change.type from frontmatter.
Plan file: chg-<workItemRef>-plan.md
Folder pattern: doc/changes/YYYY-MM/YYYY-MM-DD--<workItemRef>--<slug>/
</discovery_rules>
<source_extraction>
From the change documentation folder for this change (at minimum the change spec and implementation plan, and when present the per-change test plan, execution notes, and examples.json):
- Functional capabilities (F-#) actually delivered (cross-check against acceptance criteria evidence AC-* PASSED lines).
- Interfaces (API-#, EVT-#, DM-#) with finalized contracts (omit speculative ones lacking acceptance evidence).
- NFRs (NFR-#) that modify or add system-wide thresholds.
- Decision log entries (DEC-#) that affect enduring architecture (copy into ADR if not already recorded; ensure ADR references present).
- Data model changes (DM-#) confirmed by implementation steps.
- Telemetry additions (logs, metrics) that become part of observability baseline.
- Security/privacy changes.
<target_updates> System documentation areas potentially updated:
/doc/spec/features/— Each enduring behavior mapped to a feature spec file (create or update). File naming:feature-<slug-or-domain>-<short>.md./doc/spec/api/— Update endpoint descriptions. Synchronize with OpenAPI under/doc/contracts/rest/openapi.yaml./doc/spec/nonfunctional.md— Merge new/updated NFR thresholds./doc/contracts/rest/openapi.yaml&/doc/contracts/events/asyncapi.yaml— Add/modify operations/events./doc/contracts/events/schemas/— Add new payload schema files if events created./doc/domain/events-catalog.md— Insert or update domain event descriptions./doc/quality/test-specs/— Ensure test spec entries exist for each acceptance criterion referencing workItemRef.- Cross-links: Update front matter with
links.related_changes: ["<workItemRef>"]and link ADRs.
<front_matter_update_rules>
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.
- today First seen · 877 lines · 10 tokens per session scan A c01e9d264259
sync-docs is a command published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (37 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 8,709 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-09-07.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
discuss
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
amend-plan
Plan Amend - Discuss and apply amendments to a plan.json implementation plan.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.