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 skills add nota-america/forgecat-agent-profiles --skill sox-testinggit clone --depth 1 https://github.com/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/sox-testing)<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/sox-testing"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/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.
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/sox-testing"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/sox-testing.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.02043 |
| Opus 5 | $0.00032 | $0.01022 |
| Sonnet 5 | $0.00013 | $0.00409 |
| Haiku 4.5 | $0.00006 | $0.00204 |
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 5d 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.
This is a copy
97% identical to sox-testing — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 222 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 (
.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_finance/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] |
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
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.
- 5d ago First seen · 222 lines · 65 tokens per session scan A 952435828318
sox-testing is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 2,043 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to sox-testing, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
policy-creation
Guide for adding new enterprise policies to Chromium. Complete guide for policy definitions, pref mapping, and writing tests.
ring:adding-multi-tenancy
Adding database-per-tenant isolation into a Go service end-to-end via an 11-gate cycle: detects the stack, audits compliance, then dispatches backend agents to implement tenantId-from-JWT routing through the lib-commons v5 dispatch layer (config, middleware, repositories, metrics, tests) and runs reviewers. Use when…
dt-sec-insights
Query and analyze Dynatrace security data in security.events with DQL: vulnerabilities, threat detections, compliance posture, and scan coverage. Covers Dynatrace-native Runtime Vulnerability Analytics (RVA — CVEs, reachability, exposure, exploit), Runtime Application Protection (RAP), Automated Detections, and…
ring:testing-skills-with-subagents
Hardening a skill so it resists rationalization under pressure: run combined-pressure scenarios on a subagent without the skill (RED), capture excuses verbatim, write/edit the skill (GREEN), then plug loopholes (REFACTOR) until compliance holds. Use when deploying or editing a discipline-enforcing skill that an agent…
benchmark-task
Create a task for the LegalWork model benchmark from a description. Use when the user wants to "create/add a benchmark task", "make a new eval or test case", "turn this into a benchmark task", or "add this to the benchmark" — i.e. define a legal task with instructions and pass/fail criteria to compare how connected…
lians-integrate
Wire Lians memory into an existing agent codebase, test-first and minimal-diff. Use when the user asks to add persistent/compliance memory to their agent, integrate Lians, or replace a vector store with bitemporal memory.