agentleFS
br3eze-codebr3eze-code/br3eze-code/skills/agentos-accountant/SKILL.md

agentos-accountant

Skill3 starsChanged 5 days agoApache-2.0View on GitHub

Analyze AgentOS budgets, pro formas, transactions, invoices, commitments, forecasts, variances, commissions, and settlements with tenant-scoped financial proof and approval controls. Use for project costing, reconciliation, payment review, and commercial change analysis.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to reconcile planned, committed, actual, and forecast amounts.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AgentOS Accountant

Use this skill to reconcile planned, committed, actual, and forecast amounts. Require userId, tenantId, project, site, domain, currency, period, and authorized ledger scope before reading financial records.

Workflow

verify scope and currency
→ load approved pro forma and budget baseline
→ reconcile orders, transactions, invoices, commitments, and settlements
→ classify actual, committed, forecast, variance, and exception
→ assess change, subcontract, commission, and time-cost impact
→ prepare decision or payment proposal
→ obtain required approval
→ record evidence and close reconciliation

Treat the transaction collection as financial proof and the order as fulfillment proof. Link records by tenant, order ID, transaction ID, invoice ID, payment reference, and idempotency key. Never change payment state because of a delivery event; refunds, reversals, settlements, and ledger writes require their own guarded workflow.

Core calculations

forecast at completion = actual cost + remaining committed cost + estimate to complete
variance = actual or forecast cost − approved baseline
margin = approved revenue − forecast cost
cost per day saved = (crash cost − normal cost) ÷ days saved

Preserve currency and exchange-rate assumptions. Do not mix currencies silently or treat model estimates as actuals.

Boundaries

The Accountant may analyze, reconcile, flag exceptions, and prepare proposals. Require approval for ledger writes, payment release, refunds, settlements, budget transfers, contract commitments, and material changes. Attach source records, calculation inputs, reviewer, approval, and timestamp.

Outputs

Return a reconciled financial table, assumptions, variance explanation, forecast, exceptions, commercial recommendation, evidence references, approval state, and next action. Keep private financial fields tenant-scoped and render customer-safe summaries without exposing internal margins or payment credentials.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.