Codex Harness Engineering
v0.1.0基于 OpenAI《Harness Engineering》实践的 Codex 工作规范。强调环境能力补齐、仓库即记录系统、严格分层架构、可观测可验证闭环、持续防漂移治理。
⭐ 1· 55·0 current·0 all-time
byJimmyPeng@jimmypeng4ios
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description match the SKILL.md: it's a set of operational rules for integrating Codex into a development lifecycle (PR loops, linters, doc layout, observability). The instructions' capabilities (creating PRs, using gh/locals scripts, querying metrics) are consistent with that purpose.
Instruction Scope
The document tells agents to initiate PRs, self-review changes, use repo tools (gh), start instances with git worktree, expose logs/metrics temporarily, and run background drift-scanning tasks. These instructions are broad and can result in writing to repositories, invoking CI, or querying monitoring systems — all coherent with the stated goals but granting significant operational scope to any agent that actually has those permissions.
Install Mechanism
No install spec or code files are present; this is instruction-only, so no artifacts are downloaded or written by the skill itself.
Credentials
The SKILL.md implicitly relies on tooling and credentials (git/GitHub push/PR rights, CI access, monitoring/log access for PromQL/LogQL) but the registry metadata declares no required env vars or credentials. The implicit requirement for repository and monitoring access is not surfaced in the skill manifest, which could mislead users about what permissions an agent will need to realize these practices.
Persistence & Privilege
The skill does not request always-on presence, but it recommends periodic/background tasks (drift scanning, scheduled PRs). If an agent is permitted to act autonomously and has the stated permissions, this guidance supports ongoing autonomous actions. That behavior is consistent with the document's goals but increases operational risk when combined with broad agent permissions.
Assessment
This file is a policy/operational playbook, not an executable package — it won't install code or ask for credentials itself. However, it instructs an agent to perform actions that require real permissions (create PRs, push to repos, query logs/metrics, run background scans). Before using these guidelines with an agent, validate and restrict the agent's actual permissions: limit repository write/merge rights, provide least-privilege monitoring read access if needed, and prefer human review gates for destructive or wide-reaching automated PRs. Also be aware the manifest does not declare any credentials — you should explicitly provision and audit any tokens the agent will use.Like a lobster shell, security has layers — review code before you run it.
latestvk97exbtx10xxctrtsv5tv1qevn84fbme
License
MIT-0
Free to use, modify, and redistribute. No attribution required.