Accountsos
WarnAudited by ClawScan on May 10, 2026.
Overview
This accounting skill is coherent, but it gives an agent broad authority to create or change financial records and upload sensitive documents to an external service without visible approval safeguards.
Install only if you trust AccountsOS with your company’s accounting records. Before use, require the agent to ask before creating or changing transactions, deadlines, or document uploads; protect the API key; verify the provider; and keep an audit trail or backup of bookkeeping changes.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could add or alter bookkeeping entries, which could make VAT, tax, balances, or business records inaccurate.
The skill documents direct API actions that create and update accounting records. These are purpose-aligned, but financial record mutation is high-impact and the supplied text does not show confirmation, undo, or scope limits before writes.
"name": "create_transaction" ... "amount": 127.50 ... and "name": "update_transaction" ... "transaction_id": "uuid"
Require explicit user confirmation before any create, update, upload, or deadline-changing action. Use audit logs, backups, and the most restricted API key available.
Anyone or any agent process with this key may be able to view or modify the company’s AccountsOS records, depending on provider-side permissions.
The skill needs a bearer API key for an accounting service. This is expected for the integration, but the key likely grants access to sensitive company accounting data and actions.
Requires ACCOUNTSOS_API_KEY ... Authorization: Bearer your_api_key
Generate and store the API key securely, avoid exposing it in chat or logs, rotate it if leaked, and prefer a scoped or read-only key if the service supports one.
The agent could create an account using the user’s company and email details and receive ongoing account credentials before the user has reviewed the setup.
The onboarding flow is explicitly agent-oriented and can create a third-party accounting account and receive an API key before the human claims it. The visible text does not require user approval before this identity/account action.
Self-Signup (recommended) — Create an account yourself with one request ... Response includes `api_key` for immediate use. Your human gets a welcome email to claim the account.
Have the user create or approve the account setup manually, or require explicit confirmation before using the self-signup endpoint.
Selected financial documents may be uploaded to AccountsOS and handled under that provider’s security, retention, and privacy practices.
The skill supports sending accounting documents to an external provider API. This is aligned with the stated bookkeeping purpose, but receipts, invoices, and contracts can contain sensitive business and personal data.
Document storage — Receipts, invoices, contracts ... "name": "upload_document", "arguments": { "file_name": "receipt.pdf", "file_data": "base64_encoded_data" }Upload only documents the user chooses, verify the provider’s privacy and retention terms, and avoid broad or automatic local file uploads.
The user has less independent registry-level information to verify who operates the accounting service before granting access to financial data.
The registry metadata does not provide a source repository or homepage, while the skill asks the agent to interact with an external finance API. This is a provenance gap rather than proof of unsafe behavior.
Source: unknown; Homepage: none
Verify the accounts-os.com domain, provider identity, and terms before entering company information or API credentials.