close-review

close-review is a command for Claude Code from avelikiy/great_cto. It costs 43 tokens per session (598 once invoked), scanned A, original, MIT.

A month-end accounting review that checks whether a project's ledger and revenue records follow accounting and control requirements.

In plain words
What is it for?
Use it to review ASC 606 revenue recognition, period locks, journal integrity, and SOX ITGC gaps. ASC 606 is the accounting standard for revenue from customer contracts.
Why use it?
It helps identify errors in double-entry bookkeeping, revenue recognition, period closing, and IT controls before financial reporting.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the great-cto plugin — 40 skills, 44 commands, 70 agents shipped together

Good fit Use it to review ASC 606 revenue recognition, period locks, journal integrity, and SOX ITGC gaps. ASC 606 is the accounting standard for revenue from customer contracts.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/avelikiy/great_cto/close-review
Install

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.

Clone the repo
git clone --depth 1 https://github.com/avelikiy/great_cto

Made for: Claude Code.

Or install great-cto, the plugin that ships this one along with the rest of its 40 skills, 44 commands, 70 agents.

Wrote 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.

agentmods badge for close-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/avelikiy/great_cto/close-review/github.svg)](https://agentmods.dev/commands/avelikiy/great_cto/close-review)
Your own site
<a href="https://agentmods.dev/commands/avelikiy/great_cto/close-review"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/close-review/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.

agentmods 80×15 button for close-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/avelikiy/great_cto/close-review"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/close-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 598 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00598
Opus 5 $0.00022 $0.00299
Sonnet 5 $0.00009 $0.00120
Haiku 4.5 $0.00004 $0.00060

Measured 6d ago against content hash b19e9f562a5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

close-review 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 6d 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.

commands/close-review.md · 56 lines

What it actually says

You are the great_cto /close-review command. Run the accounting-reviewer on the current project and report findings.

Step 1 — Locate ARCH doc

ARGS="${ARGUMENTS:-}"
SLUG="$ARGS"
if [ -z "$SLUG" ]; then
  ARCH=$(ls docs/architecture/ARCH-*.md 2>/dev/null | sort -V | tail -1)
  [ -z "$ARCH" ] && echo "BLOCKED: no ARCH doc; run /architect first" && exit 1
  SLUG=$(basename "$ARCH" .md | sed 's/^ARCH-//')
else
  ARCH="docs/architecture/ARCH-${SLUG}.md"
  [ ! -f "$ARCH" ] && echo "BLOCKED: $ARCH not found" && exit 1
fi
echo "Reviewing: $ARCH"

Step 2 — Detect accounting/GL signals (skip if none)

ACCT_HITS=$(grep -ciE "general ledger|\bgaap\b|asc.?606|journal entry|month.?end close|chart of accounts|1099|three.?way reconciliation|revenue recognition|sox.itgc" "$ARCH" .great_cto/PROJECT.md 2>/dev/null || echo 0)
if [ "$ACCT_HITS" -eq 0 ]; then
  echo "No accounting/GL signals in ARCH or PROJECT.md — skipping close review."
  exit 0
fi

Step 3 — Invoke accounting-reviewer

Use the Agent tool with subagent_type: accounting-reviewer and prompt:

Review docs/architecture/ARCH-${SLUG}.md and .great_cto/PROJECT.md. Produce docs/sec-threats/TM-accounting-${SLUG}.md using the template at skills/great_cto/templates/TM-accounting.md. Report critical/high findings and append the HANDOFF block. Verdict: signed-off or blocked.

Step 4 — Surface verdict

After agent completes, print:

  • TM file path
  • Critical / High counts
  • Verdict (signed-off | blocked)
  • List of gates raised (gate:close-signoff, …)
  • Next action: if blocked → fix critical items, re-run; if signed-off → notify controller/finance lead to approve gate:close-signoff.
Changes

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.

  1. 6d ago First seen · 56 lines · 43 tokens per session scan A b19e9f562a5b

Subscribe to this mod's changes

close-review is a command published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 598 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-09-03.