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 skills/mataeil/ooda-loop/run-deploynpx skills add mataeil/OODA-loop --skill run-deploygit clone --depth 1 https://github.com/mataeil/OODA-loopWhat 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 | $0.00038 | $0.02081 |
| Opus 5 | $0.00019 | $0.01040 |
| Sonnet 5 | $0.00008 | $0.00416 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
run-deploy 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 2d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
run-deploy: GitHub Actions Deployment Trigger
The "hand" of the harness. Validates deployment readiness, fires the configured
GitHub Actions workflow via workflow_dispatch, monitors completion, and
verifies the service is healthy afterward.
- NEVER auto-invoked without passing the full pre-deploy checklist
- Requires explicit conditions — does not deploy blindly
- Writes results to
agent/state/deploy.json
Safety Rules
- HALT file — Mandatory first check. If present, print reason and stop.
- Pre-deploy checklist — All six conditions must pass before triggering.
- gh required — Cannot deploy without GitHub CLI. If unavailable, error and exit.
- No blind deploys —
config.deploy_workflowmust be explicitly configured.
Step 0: Safety
0-A: HALT Check
if file exists at config.safety.halt_file:
Print "[HALT] run-deploy stopped. Reason: {file_content}"
EXIT immediately.
0-B: Config Validation
if config.deploy_workflow is missing, null, or empty:
Print "No deploy workflow configured. Skipping."
EXIT cleanly (not an error).
Step 1: Pre-Deploy Checklist
All six conditions must pass. On first failure, print the reason and skip deployment.
| # | Check | Source | Pass Condition |
|---|---|---|---|
| 1 | No critical health alerts | agent/state/service_health.json |
alerts has no item with severity == "critical" |
| 2 | Tests passing | agent/state/test_coverage.json |
status == "passing" |
| 3 | No HALT file | config.safety.halt_file |
File does not exist (re-confirmed) |
| 4 | Complexity level | config.json |
progressive_complexity.current_level >= 3 OR invoked directly by user |
| 5 | Clean working tree | git status --porcelain |
Output is empty (no uncommitted changes) |
| 6 | Workflow file exists | .github/workflows/{deploy_workflow} |
File exists in the repository (prevents cryptic GitHub API errors) |
On any failure:
Pre-deploy checklist FAILED: {reason}
Deployment skipped.
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.
- 2d ago First seen · 231 lines · 38 tokens per session scan A 52d377f13add
run-deploy is a skill published in the GitHub repository mataeil/OODA-loop (5 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 2,081 once invoked, about $0.0002 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-31.
Other skills, from other repositories
paper-illustration
Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Claude-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…