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 commands/ai-sdlc-framework/ai-sdlc/orchestrator-tickgit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/ai-sdlc-framework/ai-sdlc/orchestrator-tick)<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/orchestrator-tick"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/orchestrator-tick.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.00196 | $0.16992 |
| Opus 5 | $0.00098 | $0.08496 |
| Sonnet 5 | $0.00039 | $0.03398 |
| Haiku 4.5 | $0.00020 | $0.01699 |
Grade A, and why
orchestrator-tick 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 — 1,238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run one autonomous orchestrator tick in the current Claude Code session as Conductor (RFC-0041 §4.2).
This command shifted in RFC-0041 Phase 1 (AISDLC-377.1). The previous behavior
invoked Agent directly to dispatch dev subagents in-session. The original
RFC-0041 §2.1 rationale cited a "600s background-agent watchdog (~85% kill
rate)" — that claim was a misdiagnosis (forensic re-measurement
2026-05-21 via python3 ~/.claude/skills/audit-subagent/audit.py found 0
watchdog kills and 80.8% clean completion across 73 dev subagents, median
16 min, max 2.5 h). The Conductor/Worker decoupling pattern provides real
benefits (operator-controlled parallelism, billing visibility, cost-pool
isolation post-2026-06-15) that stand independently of the now-corrected
watchdog claim; this command continues to use the pattern for those reasons.
The cost-pool comparison should be re-evaluated against the corrected
baseline.
Why this lives in the slash command body (not a subagent). Plugin subagents cannot use the
Agenttool — Claude Code filters it out one level deep. The reviewer fan-out per verdict must therefore happen here.
Hard rules (identical to /ai-sdlc execute)
- Never merge any PR. Do not run
gh pr merge. - Never force-push. Use
--force-with-leaseonly after the mandatory rebase. - Never close PRs or issues. No
gh pr close,gh issue close. - Never delete branches. No
git branch -D/-d. - Never edit
.ai-sdlc/**..github/workflows/**is only refused when the project's.ai-sdlc/agent-role.yamllists it underblockedPaths— not blocked by default. - Never run
git reset --hardad-hoc. The sanctioned path isscripts/check-orchestrator-state.sh, which resets the parent toorigin/mainONLY when the working tree is clean. Outside that script,git reset --hardis forbidden unless the operator explicitly authorizes it in the current session. (AISDLC-450) - Never write CI-skip tokens (
[skip ci],[ci skip], etc.) in commits.
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 Changed 069eb73ab78c
- 6d ago First seen · 1,238 lines · 196 tokens per session scan A 95339e61a2a1
orchestrator-tick is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (103 stars, last pushed today), licensed Apache-2.0. It adds 196 tokens to every session and 16,992 once invoked, about $0.0010 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 commands, from other repositories
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
research
Research a technical or product question.
profile
Profile Go code, identify bottlenecks, optimize, and verify improvements.
wardley
Create strategic Wardley Maps for architecture decisions and build vs buy analysis.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
eu-dora
You are helping an enterprise architect generate a DORA Compliance Assessment (Digital Operational Resilience Act, EU Regulation 2022/2554) for a financial sector entity operating in the European Union. DORA has applied since 17 January 2025 and establishes a unified framework for ICT risk management, incident…