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 skills add miniidealab/openlogos --skill deployment-executorgit clone --depth 1 https://github.com/miniidealab/openlogosWrote 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/skills/miniidealab/openlogos/deployment-executor)<a href="https://agentmods.dev/skills/miniidealab/openlogos/deployment-executor"><img src="https://agentmods.dev/badge/skills/miniidealab/openlogos/deployment-executor/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/skills/miniidealab/openlogos/deployment-executor"><img src="https://agentmods.dev/badge/skills/miniidealab/openlogos/deployment-executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.01971 |
| Opus 5.5 | $0.00005 | $0.00788 |
| Sonnet 5.5 | $0.00003 | $0.00394 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
deployment-executor 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Deployment Executor
在
openlogos verify通过后，按已合并的部署方案执行经人类明确确认的部署任务，并引导运行openlogos smoke。该 Skill 只在部署执行阶段使用。
触发条件
- 用户明确要求执行部署
- 用户说“按部署方案部署”“执行当前提案的部署任务”“部署到 staging / production”
- 当前提案
tasks.md存在[deploy]section - Initial 阶段 verify 通过后需要部署到目标环境
前置依赖
- 用户明确授权部署
logos/resources/prd/3-technical-plan/3-deployment/中存在部署方案- 当前提案已
VERIFY_PASS - 当前提案
tasks.md中存在[deploy]section - 部署所需命令、环境变量和回滚策略已在部署方案中声明
如果任一条件不满足，停止并说明缺少哪一项。
部署授权来源（change-flow-redesign）
插入到「前置依赖」之后。本节修订「前置依赖」第 1 条与「禁止行为」第 1 条对"部署必须用户明确授权 / 禁止自动部署"的绝对表述，明确在无人值守模式下的受限授权来源。
部署执行的授权可来自以下两者之一：
- 默认 / 手动模式（半自动）：用户明确授权部署（前置依赖原义；生产环境强烈建议走此路径）。半自动下部署执行、
openlogos smoke等仍逐次须人类明确授权，行为完全不变。 - 无人值守
openlogos next --auto模式（全自动 / standing 授权）：--auto的含义被重定义为一次性的 standing run-scoped 授权——用户选择--auto即在本次运行域内一次性授权全链路自动到底。本次next --auto响应对 deliver 入口门（deliver-entry，skippable:true）输出gate_auto_passed === true时，即构成对本次部署的放行依据（部署目标可能是测试环境而非生产）。
全自动 --auto 下，同一 standing 授权也覆盖"代码已绿后的盖章 / 发布"动作：部署完成后的 openlogos smoke、以及更下游的 git push（plugin/bin/guard-check 的安全白名单本就放行 git push，无需任何 marker / guard 改动，全自动下纯由指令文本授权）均可经此授权自动执行，无需逐次人类再确认；可跳门每次放行向 GATE_AUTO_PASSED 追加一行审计。
受限约束（必须遵守）：
- 授权依据是**本次
--auto响应的gate_auto_passed === true**这一 live 决策，不是GATE_AUTO_PASSED文件的存在；历史审计行不构成对后续部署 / smoke / push 的授权（与默认next忽略GATE_AUTO_PASSED一致）。 - 仍须满足其它前置依赖（
VERIFY_PASS、部署方案、[deploy]section、部署决策无冲突）。 - 仍禁止：跳过部署方案凭经验执行、部署失败后写
DEPLOY_DONE、手写DEPLOY_DONE、跳过需要的 smoke（全自动只是把 smoke 的"授权"前置到用户选择--auto，并不允许略过 smoke 本身）。 - 硬红线不受
--auto影响：代码未收敛 / 未绿（gate:implement:loop-exhausted）在任何模式下都绝不自动放行，自动放行只发生在"代码已绿"之后。 - 部署完成后仍调用
openlogos deploy-done受控落标，不手写 marker。
据此，「前置依赖」第 1 条「用户明确授权部署」在
--auto下由「本次响应gate_auto_passed=true」满足；「禁止行为」第 1 条「未经用户明确确认自动部署」的"明确确认"在--auto下等价于用户选择--auto+ 本次放行，而非凭 AI 自行决定。
核心能力
- 读取部署方案和当前提案部署任务
- 将部署任务拆解为可执行步骤
- 在关键命令前说明目的、影响环境和回滚点
- 执行部署命令并记录结果
- 生成部署报告
- 写入部署完成标记
- 引导用户运行
openlogos smoke
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 Changed · +4 lines · +13 tokens per session 1853ef551bd6
- 1mo ago First seen · 175 lines · 0 tokens per session scan A f72aee7518a5
deployment-executor is a skill published in the GitHub repository miniidealab/openlogos (322 stars, last pushed 4d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,971 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.