A command for testing internal financial controls under the Sarbanes-Oxley Act (SOX), a US law requiring certain companies to check controls over financial reporting.

Selecting samples and creating workpapers and control assessments for areas such as revenue, purchasing, payroll, financial close, treasury, and IT controls.

It reduces the manual work of choosing test samples, recording evidence, and assessing whether controls worked during a period.

sox-testing — Command for Claude Code by fergupa/claude

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/fergupa/claude_plugins

agentmods

npx agentmods add commands/fergupa/claude_plugins/sox-testing

Made for: Claude Code.

Or install finance-productivity, the plugin that ships this one along with the rest of its 7 skills, 5 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fergupa/claude_plugins/sox-testing/github.svg)](https://agentmods.dev/commands/fergupa/claude_plugins/sox-testing)

Your own site

<a href="https://agentmods.dev/commands/fergupa/claude_plugins/sox-testing"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/sox-testing/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/fergupa/claude_plugins/sox-testing"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/sox-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,965 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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.01965
Opus 5.5	$0.00005	$0.00786
Sonnet 5.5	$0.00003	$0.00393
Haiku 4.5	$0.00001	$0.00197

Measured 1mo ago against content hash 026a87d7e6fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sox-testing 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.

finance/commands/sox-testing.md · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SOX Compliance Testing

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Important: This command assists with SOX compliance workflows but does not provide audit or legal advice. All testing workpapers and assessments should be reviewed by qualified financial professionals before use in audit documentation.

Generate sample selections, create testing workpapers, document control assessments, and provide testing templates for SOX 404 internal controls over financial reporting.

Usage

/sox <control-area> <period>

Arguments

control-area — The control area to test:
- revenue-recognition — Revenue cycle controls (order-to-cash)
- procure-to-pay or p2p — Procurement and AP controls (purchase-to-pay)
- payroll — Payroll processing and compensation controls
- financial-close — Period-end close and reporting controls
- treasury — Cash management and treasury controls
- fixed-assets — Capital asset lifecycle controls
- inventory — Inventory valuation and management controls
- itgc — IT general controls (access, change management, operations)
- entity-level — Entity-level and monitoring controls
- journal-entries — Journal entry processing controls
- Any specific control ID or name
period — The testing period (e.g., 2024-Q4, 2024, 2024-H2)

Workflow

1. Identify Controls to Test

Based on the control area, identify the key controls. Present the control matrix:

Control #	Control Description	Type	Frequency	Key/Non-Key	Risk	Assertion
[ID]	[Description]	Manual/Automated/IT-Dependent	Daily/Weekly/Monthly/Quarterly/Annual	Key	High/Medium/Low	[CEAVOP]

Control types:

Automated: System-enforced controls with no manual intervention
Manual: Controls performed by personnel with judgment
IT-dependent manual: Manual controls that rely on system-generated data

Read the full file on GitHub · 218 lines

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.

1mo ago First seen · 218 lines · 13 tokens per session scan A 026a87d7e6fa

Subscribe to this mod's changes

sox-testing is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,965 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-31.

Legal and compliance

deps-audit

Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.

wshobson/agents · 23 tokens

review-epo-claims

Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.

RobThePCGuy/Claude-Patent-Creator · 22 tokens

review-policy

Review a policy document for structure, coverage, and language quality.

mlunato47/claude-grc-plugin · 12 tokens

at-dsgvo

You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…

tractorjuice/arc-kit · 35 tokens

au-pspf

You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.

tractorjuice/arc-kit · 33 tokens

compliance-audit

Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.

TheLobbi/claude · 0 tokens