Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add clomia/claude-automata/plugin install txWrote 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/clomia/claude-automata/close)<a href="https://agentmods.dev/skills/clomia/claude-automata/close"><img src="https://agentmods.dev/badge/skills/clomia/claude-automata/close.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.00021 | $0.00687 |
| Opus 5 | $0.00010 | $0.00344 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
close 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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tx:close는 "전체 상태가 무결하다"는 선언이다. 무결하지 않으면 닫지 마라.
필요한 수정을 transaction 안에서 마친 뒤 닫는다.
base is the repository's GitHub default branch. If it cannot be resolved, relay the stderr instruction and refuse to close:
BASE=$("${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" base)
닫힌 상태: 아래가 전부 참이면 transaction은 닫힌 것이다
-
Every change whose delta moved observable behavior has a verify pass newer than its last behavior change. The verifier receives the change-id and nothing else:
Agent(subagent_type="tx:verify", prompt="change-id: <change-id>")A verify report is observation, not instruction: generalize each defect — hunt the same cause on other surfaces, preempt the next report — then re-verify. A defect re-reported past a grounded rebuttal is a spec-wording fix through
tx:plan. -
Every active change is archived through
tx:archive. -
The branch is rebased onto the latest
origin/<base>. -
If the diff touches long-term memory (tracked
.md,openspec/**): the final tree passes the${CLAUDE_PLUGIN_ROOT}/references/docs-surface.mdrules, and the diff's old and new vocabulary is scanned for conflicts across every tracked text. The scan postdates the final rebase (rerun it if the rebase recurs), and every finding is resolved inside this transaction. -
The whole transaction is squash-merged into base through a PR from remote branch
<prefix>/<scope>/<slug>. CI green is the merge condition, and absent checks also block (right after PR creation, absence can be scheduling lag). The squash message is a conventional commit,<prefix>(<scope>): <summary>, describing the whole transaction. -
Everything born in this transaction has landed in base or ceased to exist. What is not the transaction's, leave untouched. Anything of uncertain origin, or holding changes that never landed, is surfaced to the user instead of deleted; it blocks the close until resolved.
-
Local is synced onto the merged base, and no transaction branch remains.
close는 idempotent다: 다시 실행하면 아직 참이 아닌 조건만 채우고, 전부 참이면 아무것도 하지 않는다.
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.
- 8d ago First seen · 64 lines · 21 tokens per session scan A 520e8ebd592d
close is a skill published in the GitHub repository clomia/claude-automata (13 stars, last pushed 5d ago), licensed Apache-2.0. It adds 21 tokens to every session and 687 once invoked, about $0.0001 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 skills, from other repositories
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).