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/warroom-ceo/core/sox-testingnpx skills add WARROOM-CEO/CORE --skill sox-testinggit clone --depth 1 https://github.com/WARROOM-CEO/COREWhat 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.00076 | $0.02081 |
| Opus 5 | $0.00038 | $0.01040 |
| Sonnet 5 | $0.00015 | $0.00416 |
| Haiku 4.5 | $0.00008 | $0.00208 |
Grade A, and why
sox-testing-th 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 3d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language: All user-facing output — responses, summaries, and any text the user will read — must be written in Thai (ภาษาไทย). Internal logic, file paths, code snippets, and technical values remain in English.
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-payorp2p— Procurement and AP controls (purchase-to-pay)payroll— Payroll processing and compensation controlsfinancial-close— Period-end close and reporting controlstreasury— Cash management and treasury controlsfixed-assets— Capital asset lifecycle controlsinventory— Inventory valuation and management controlsitgc— IT general controls (access, change management, operations)entity-level— Entity-level and monitoring controlsjournal-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] |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 221 lines · 76 tokens per session scan A c5f0539293b6
sox-testing-th is a skill published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 5mo ago), licensed MIT. It adds 76 tokens to every session and 2,081 once invoked, about $0.0004 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
advogado-criminal
Advogado criminalista especializado em Maria da Penha, violencia domestica, feminicidio, direito penal brasileiro, medidas protetivas, inquerito policial e acao penal.
mod-actions
Comprehensive moderation toolkit: user actions (ban/mute/DM), strike system, image moderation, report handling, generation moderation, content/training moderation, and NCMEC/CSAM reporting. All via Civitai tRPC API.
auditing-part11-trails
Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic signatures, and tamper-evidence — for OpenMed pipelines in GxP and clinical-trial (GCP) settings. Use when the user runs OpenMed in a regulated/validated environment and needs an attributable, time-stamped, tamper-evident record of…
2026-legal-research-agent
Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape. Activate on "find expungement data", "scrape state laws", "legal research", "court URLs", "statute sources", "Clean Slate laws", "automatic…
amazon-suspension-appeal
Account suspension prevention and appeal — policy violations, Plan of Action writing, reinstatement process.
build-audit-logs
Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews). For application code, not for extending the evlog package.