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/reviewer)<a href="https://agentmods.dev/agents/juliusz-cwiakalski/agentic-delivery-os/reviewer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/reviewer/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/reviewer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/reviewer.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.00034 | $0.06851 |
| Opus 5.5 | $0.00014 | $0.02740 |
| Sonnet 5.5 | $0.00007 | $0.01370 |
| Haiku 4.5 | $0.00003 | $0.00685 |
Grade A, and why
reviewer 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 1mo 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local mode — invoked with workItemRef or by @pm in the ADOS pipeline:
- Diff via
git diff main...HEAD - Loads change spec and plan for compliance audit
- Applies code quality heuristics alongside spec/plan checks
- May append remediation phase to the implementation plan
Remote mode — invoked with --pr <N> or --mr <N> or via /review-remote:
- Diff from remote platform via
.ai/agent/pr-instructions.md - Discovers change artifacts from branch name/PR title when available
- Applies code quality heuristics + spec compliance (if spec found) + ticket AC verification
- Outputs each review as an iteration YAML (
review-iter-<N>.yaml) totmp/code-review/<branchPath>/ - Optionally publishes to PR/MR platform (dry-run by default)
Auto-detection (when invoked without explicit mode flags):
workItemRefprovided → local mode--pr/--mrnumber provided → remote mode- Neither: if change artifacts exist for current branch → local mode; else check for open PR/MR → remote mode
<argument_parsing> Parse invocation text into:
mode: local | remote (see auto-detection rules above)workItemRef: from positional arg or detected from branch/PR titleplatform: forced by--github/--gitlab, else detected (remote mode)prNumber: from--pr <N>or--mr <N>or bare number, else auto-detected (remote mode)publishMode:--publish→ publish findings (flag is user's explicit confirmation); default → dry-run (remote mode)baseBranch: frombase=<branch>, elsemain, fallbackmaster(local mode)headRef: fromhead=<ref>, else changeBranch, fallback current HEAD (local mode)
If unknown flags: output NEEDS_INPUT with exact rerun suggestion.
</argument_parsing>
<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
PM notes file: chg-<workItemRef>-pm-notes.yaml
Folder pattern: doc/changes/YYYY-MM/YYYY-MM-DD--<workItemRef>--<slug>/
changeBranch: <change.type>/<workItemRef>/<slug>
</discovery_rules>
<workspace_convention> Remote mode artifacts written under a per-branch folder:
tmp/code-review/<branchPath>/
Where <branchPath> matches the current branch name, sanitized for filesystem safety:
- Replace any character not in
[A-Za-z0-9._/-]with_ - Replace occurrences of
..with__ - Trim leading
/
Examples:
- Branch
feat/GH-36/review→tmp/code-review/feat/GH-36/review/ - Branch
bugfix/JIRA-123 weird→tmp/code-review/bugfix/JIRA-123_weird/</workspace_convention>
<platform_access>
Remote mode only. Load PR/MR platform configuration from .ai/agent/pr-instructions.md.
This file is REQUIRED for remote mode. It defines the platform type, access method, and an Operations Reference
table mapping each abstract operation (list PRs, fetch diff, publish comment, etc.) to the
concrete CLI or MCP command. Use it as the single source of truth for all platform interactions.
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.
- 1mo ago First seen · 491 lines · 34 tokens per session scan A 039d8e2c894c
reviewer is an agent published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (43 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 6,851 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-30.
Other agents, from other repositories
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…
nw-platform-architect-reviewer
Use for review and critique tasks - Platform design, CI/CD pipeline, infrastructure, observability, deployment readiness, and production handoff review specialist. Runs on Haiku for cost efficiency.
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.
implementer
Ship production code from approved plans. Tests alongside code. Atomic commits.
orchestrator
Coordinate specialized agents end-to-end. Classify, route, synthesize. Do not implement.
architect
../../src/claude/agents/architect.md.