audit-support

audit-support is a skill for Claude Code from alebgl77/claude-inc. It costs 101 tokens per session (1,119 once invoked), scanned A, original, MIT.

A preparation workflow for an external audit, where independent reviewers check whether financial records are supported and presented properly. It organizes requested documents, process explanations, sample evidence, balance checks, open tasks, and responses to findings.

In plain words
What is it for?
Use it to prepare the auditor’s PBC list, document revenue, purchasing, and payroll processes, match requested samples to support, build tie-outs, track missing items, and draft responses to findings.
Why use it?
It replaces a scattered audit-preparation process with a tracked list of evidence, owners, deadlines, and unresolved questions. It also helps connect business processes to accounting records and controls.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-inc plugin — 64 skills, 3 commands, 11 agents shipped together

Good fit Use it to prepare the auditor’s PBC list, document revenue, purchasing, and payroll processes, match requested samples to support, build tie-outs, track missing items, and draft responses to findings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alebgl77/claude-inc/audit-support
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.

Any agent
npx skills add alebgl77/claude-inc --skill audit-support
Clone the repo
git clone --depth 1 https://github.com/alebgl77/claude-inc

Made for: Claude Code.

Or install claude-inc, the plugin that ships this one along with the rest of its 64 skills, 3 commands, 11 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 audit-support

README.md
[![agentmods](https://agentmods.dev/badge/skills/alebgl77/claude-inc/audit-support/github.svg)](https://agentmods.dev/skills/alebgl77/claude-inc/audit-support)
Your own site
<a href="https://agentmods.dev/skills/alebgl77/claude-inc/audit-support"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/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.

agentmods 80×15 button for audit-support

Your own site · 80×15
<a href="https://agentmods.dev/skills/alebgl77/claude-inc/audit-support"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/audit-support.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,119 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00101 $0.01119
Opus 5.5 $0.00040 $0.00448
Sonnet 5.5 $0.00020 $0.00224
Haiku 4.5 $0.00010 $0.00112

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

Security

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

skills/audit-support/SKILL.md · 74 lines

How it starts

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

Audit Support — Auditor

"Prep for audit."

When to use

  • An audit is scheduled — "fieldwork starts August 3, get us ready".
  • The request list landed — "here's the auditor's PBC, organize and track it".
  • Samples arrived — "they picked 25 invoices, do we have support for each?".
  • Findings need answers — "draft management responses to these three findings".
  • Balances must be provable — "build tie-outs for cash, AR, and fixed assets".

Workflow

  1. Scope the audit. Period, framework, first-year vs recurring, and the areas that matter — load the TB or statements with code and rank areas by balance and activity, never by guesswork.
  2. Build the PBC list by area (cash, AR/revenue, inventory, fixed assets, AP/accruals, debt, equity, payroll, tax): each item gets description, owner, expected format, due date, status. Merge with the auditor's own list when one exists — their naming wins.
  3. Draft walkthrough narratives for revenue, purchases, and payroll: trigger event → documents created → systems touched → approvals → how it hits the GL, with control points tagged inline (e.g., [C1: 2-way match]). One page per cycle, specific to this company — no boilerplate.
  4. Match samples to support. For each sampled item, list required documents (invoice, PO/contract, delivery or acceptance evidence, payment proof), check what exists, and mark complete / partial (naming the gap) / absent. Find the gaps before the auditor does.
  5. Build tie-out schedules per tested area: GL balance → subledger or supporting schedule → financial statement line, computed in code, with differences explained or proven zero.
  6. Run the open-items tracker: item, area, requested by, owner, due date, status, blocker — sorted by due date, overdue flagged.
  7. Draft finding responses: restate the finding neutrally, give root cause, management response, and remediation with a named owner and target date. Factual and specific — no defensiveness, no over-promising.
  8. Package. Write PBC-<period>.md (or .xlsx), the walkthroughs, tie-outs, and tracker; refresh the tracker as items close.

Read the full file on GitHub · 74 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.

  1. 1mo ago First seen · 74 lines · 101 tokens per session scan A b2562109f798

Subscribe to this mod's changes

audit-support is a skill published in the GitHub repository alebgl77/claude-inc (19 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 1,119 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

company-cfo

Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to…

coreyhaines31/makerskills · 202 tokens

personal-cfo

When you want to model personal financial scenarios — house purchase + rental income (ADU, bedroom rentals, house-hacking), renovation budgets, monthly cash flow, big-purchase decisions, savings/investment what-ifs for a household. Ships with a house scenario template; other scenarios (refi, car, education…

coreyhaines31/makerskills · 209 tokens

mcp-lark

Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc.

aahl/skills · 45 tokens

crypto-report

Get cryptocurrency market data. Get Binance AI analysis report. Get blockchain news updates.

aahl/skills · 19 tokens

giasip-dispatch

A skill for sending a task to other AI models and collecting their results. It supports direct API calls, command-line tools and built-in internal agents, depending on the model.

GiaSip/giasip-skills · 162 tokens

black-swan

Activate when: user says 'this can't happen,' 'never happened in N years,' 'our models say it's near-zero'; user is stress-testing a strategy or portfolio against extreme scenarios; someone mentions fat tails, Taleb, narrative fallacy, or turkey problem; a past catastrophic event is being analyzed and it 'seemed…

deciqAI/knowledge-skills · 125 tokens