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/jh941213/codex-lattice/commit-push-prnpx skills add jh941213/codex-lattice --skill commit-push-prgit clone --depth 1 https://github.com/jh941213/codex-latticeWhat 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.00099 | $0.00611 |
| Opus 5 | $0.00049 | $0.00305 |
| Sonnet 5 | $0.00020 | $0.00122 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade B, and why
commit-push-pr scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.codex/config.toml`의 `commit_attribution`을 설정했다면 그 값을 따른다. What it actually says
커밋, 푸시, PR 생성
현재 변경사항을 커밋하고 푸시한 후 PR을 생성합니다.
Step 1: 사전 검증
# 현재 브랜치 확인 — main/master면 STOP
BRANCH=$(git branch --show-current)
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
echo "BLOCKED: main/master 브랜치에서 직접 커밋 금지"
exit 1
fi
# 상태 확인
git status
git diff --stat
git log --oneline -5
Step 2: 위험 파일 확인
# 민감한 파일이 staged 되었는지 검사
git diff --cached --name-only | grep -E '\.(env|pem|key|credentials)' && echo "WARNING: 민감 파일 포함!"
Step 3: 커밋
# 변경 파일 선택적 staging (git add -A 지양)
git add [specific-files]
# 커밋 메시지 작성
git commit -m "$(cat <<'EOF'
[타입] 제목 (50자 이내)
본문 (선택 — 무엇이 아닌 왜를 설명)
Co-Authored-By: Codex <[email protected]>
EOF
)"
Codex 기본 attribution을 쓰는 경우:
Co-Authored-By: Codex <[email protected]>
~/.codex/config.toml의 commit_attribution을 설정했다면 그 값을 따른다.
타입: feat, fix, docs, style, refactor, test, chore
Step 4: 푸시
# 원격 브랜치 설정 + 푸시
git push -u origin $(git branch --show-current)
Step 5: PR 생성
gh pr create --title "[타입] 제목" --body "$(cat <<'EOF'
## 요약
- 변경 내용 1
- 변경 내용 2
## 테스트
- [ ] typecheck 통과
- [ ] lint 통과
- [ ] test 통과
EOF
)"
출력
완료 시 PR URL을 반환합니다.
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 · 89 lines · 99 tokens per session scan B b6eb94b3eb53
commit-push-pr is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 99 tokens to every session and 611 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
release
Create a new es-toolkit release (version bump, changelog, tag).
git-workflow
安全处理 Git 状态检查、提交信息、commit、分支、push、PR 和 rebase。用于用户要求检查改动、生成或创建提交、管理分支、推送、发起 PR 或整理历史时；严格区分每个动作的授权，并保护工作树中已有和无关的修改。.
zed-cherry-pick
Cherry-pick one or more merged PRs and/or commits into Zed's preview or stable release branch. Use this whenever the user mentions cherry-picking to preview/stable, a failed cherry-pick run, or wants to manually port fix(es) into a release branch.