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 charlieviettq/awesome-agent-skill --skill audit-supportgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/audit-support)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/audit-support"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/audit-support/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/charlieviettq/awesome-agent-skill/audit-support"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/audit-support.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.00045 | $0.03302 |
| Opus 5 | $0.00023 | $0.01651 |
| Sonnet 5 | $0.00009 | $0.00660 |
| Haiku 4.5 | $0.00005 | $0.00330 |
Grade A, and why
audit-support 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 9d 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
98% identical to audit-support — 4 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Support
Important: This skill 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. While "significance" and "materiality" are context-specific concepts that are ultimately assessed by auditors, this skill is intended to assist professionals in the creation and evaluation of effective internal controls and documentation for audits.
SOX 404 control testing methodology, sample selection approaches, testing documentation standards, control deficiency classification, and common control types.
SOX 404 Control Testing Methodology
Overview
SOX Section 404 requires management to assess the effectiveness of internal controls over financial reporting (ICFR). This involves:
- Scoping: Identify significant accounts and relevant assertions
- Risk assessment: Evaluate the risk of material misstatement for each significant account
- Control identification: Document the controls that address each risk
- Testing: Test the design and operating effectiveness of key controls
- Evaluation: Assess whether any deficiencies exist and their severity
- Reporting: Document the assessment and any material weaknesses
Scoping Significant Accounts
An account is significant if there is more than a remote likelihood that it could contain a misstatement that is material (individually or in aggregate).
Quantitative factors:
- Account balance exceeds materiality threshold (typically 3-5% of a key benchmark)
- Transaction volume is high, increasing the risk of error
- Account is subject to significant estimates or judgment
Qualitative factors:
- Account involves complex accounting (revenue recognition, derivatives, pensions)
- Account is susceptible to fraud (cash, revenue, related-party transactions)
- Account has had prior misstatements or audit adjustments
- Account involves significant management judgment or estimates
- New account or significantly changed process
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.
- 9d ago First seen · 375 lines · 45 tokens per session scan A 02116ac3fe9a
audit-support is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (25 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 3,302 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to audit-support, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
subcontractor-payment-tracker
Track subcontractor payments, lien waivers, and compliance. Manage payment schedules and documentation.
procurement-reviewer
Reviews a proposal, business case, deck or vendor contract in character as a Head of Procurement archetype, then saves a structured review document with a verdict, findings that cite the artifact, commercial risks and five interrogation questions. Use when the user asks for a procurement review, a commercial or…
insurance-claims
Analyze an insurance claims processing system for lifecycle completeness, straight-through processing automation, fraud detection coverage, reserve estimation methodology, subrogation recovery workflows, and regulatory compliance with state prompt payment laws..
revrec-saas
Generate an ASC 606 / IFRS 15 revenue recognition engine for SaaS — the five-step model (identify contract, identify performance obligations, determine transaction price, allocate to performance obligations, recognize as POs are satisfied) applied to subscription contracts.
credit-risk
Audit credit risk modeling software for scoring algorithm accuracy, regulatory compliance (ECOA, FCRA, SR 11-7), bias and disparate impact testing, model governance lifecycle, and explainability..
kyc-aml-screener
Generate a production-grade KYC / AML / sanctions screening pipeline for customer onboarding, transaction monitoring, and ongoing review. Triggers: "KYC", "AML", "OFAC", "sanctions screening", "PEP".