Download Fensory Agent Trade Audit Skill

Download and review

Download the public file, review every instruction, then place it in the skills directory documented by the compatible client you use. Client-specific paths are omitted until each workflow is verified.

Download

curl -fsSL https://fensory.com/skills/audit-agent-trades/SKILL.md -o SKILL.md

Install in Hermes

hermes skills install https://fensory.com/skills/audit-agent-trades/SKILL.md --name fensory-trade-audit

What the skill instructs

• Read the account and instrument before preparing an action.
• Keep the proposal inside the user's ceiling and the account's per-order cap.
• Show the exact symbol, side, order type and size before a write call. Include the limit price for a limit order, or the current quote and expected execution conditions for a market order, then ask for confirmation.
• Report a prepared order, submitted order and fill as three different states.

SKILL.md

---
name: fensory-trade-audit
description: Reconstruct a Fensory trading session from read-only account, order, fill, funding and portfolio records while keeping instructions, submissions and executions separate.
license: Proprietary
compatibility: Requires access to the Fensory MCP server and an eligible Fensory account. Fensory is not available to US persons.
metadata:
  author: Fensory AG
  version: "0.1.0"
  source: "https://fensory.com/skills/audit-agent-trades"
---

# Audit what your AI trading agent actually did

## When to use

This guide is for a user, operator or reviewer who needs to verify an agent trading session, investigate an unexpected position or build a dated record before evaluating a strategy.

It is not an audited financial statement, tax record, proof that a prompt caused every account event or a public performance leaderboard. It does not infer intent from a fill and does not label an unrealized gain as realized profit.

## Operating rules

- Start with read tools and identify the signed-in account, market, venue and instrument before preparing an action.
- Treat the Fensory account state, open orders, positions and fills as authoritative when they differ from the conversation.
- Fensory enforces four controls on the account: a kill-switch, an access expiry, a market allow-list and a per-order cap. Client confirmation instructions are separate from those account controls.
- Never describe a perpetual future as a share or tokenized equity. State the instrument and its risks before discussing an order.
- Never substitute a different market, quote currency or instrument because the requested one is unavailable.
- Keep every proposed order within both the user's stated ceiling and the account's per-order cap.
- Do not place, cancel or replace an order until the exact symbol, side, order type and size have been shown. For a limit order, show the limit price. For a market order, show the current quote and expected execution conditions. The user must confirm that exact action.
- Stop when a required tool is unavailable, the account limit cannot be verified, the quote is stale or the instrument is ambiguous.

## Risk and scope

This file is operational guidance, not financial advice. Trading can lose the full amount committed. Perpetual futures use margin and can be liquidated. Spot assets can lose value. Stop if the instrument, current quote or account controls cannot be verified.

## Procedure

1. **Freeze the scope.** The audit defines account, markets, time window and supplied instruction record before reading results. That prevents the reviewer from selecting only favorable fills or attributing unrelated activity to the agent.
2. **Read opening and current state.** Positions and balances provide the boundary conditions. A current snapshot cannot reconstruct every past state, so the output labels what is observed now and what comes from historical records. Tools: `get_account_state`, `get_spot_account_state`.
3. **Collect orders and fills.** The assistant separates order submission from execution and records partial fills and resting remainders. An order ID links the status response to the fill evidence without relying on conversational memory. Tools: `get_open_orders`, `get_order_status`, `get_fills`.
4. **Add funding, fees and portfolio history.** Funding and fees can change the result after entry, while portfolio history shows account-level movement. The audit reports these components separately before calculating any supported total. Tools: `get_funding_payments`, `get_portfolio_history`.
5. **Reconcile and flag gaps.** The final table explains every supported state change and lists records that do not reconcile. Missing history remains missing rather than being filled with an assumption about what the agent intended.

## Request template

Use only read tools to audit my Fensory trading activity from [START TIME AND TIMEZONE] to [END TIME AND TIMEZONE]. Call get_account_state, get_spot_account_state, get_open_orders, get_fills, get_funding_payments and get_portfolio_history. Use get_order_status for every order ID I provide or every relevant order ID returned by the records.

Build a chronological table with timestamp, instrument, spot or perpetual-futures surface, requested action if supplied, submitted order, status, filled size, average fill price, fee, funding payment, resulting position and evidence source. Keep “prepared”, “submitted”, “partly filled”, “filled”, “cancelled”, “rejected” and “still open” as different states.

Reconcile opening and closing account state. Flag unmatched fills, duplicate orders, open remainders, changes in leverage or margin mode, and any market outside the intended allow-list. Calculate realized trading profit or loss only when the returned records support it. Report unrealized profit or loss separately. Do not infer that the agent caused a manual trade, deposit, withdrawal or account change unless the evidence identifies that source.

Do not place, cancel, replace or close any order. Do not change leverage, limits or account settings. If the returned history is incomplete, say which record is missing and stop short of a performance conclusion.

## Failure handling

- **A tool call is mistaken for a fill:** A successful submission can leave an order open, partly filled or rejected later. Order status and fills decide what executed.
- **The conversation is treated as the ledger:** An assistant can summarize incorrectly or lose context. Use the prompt as intent evidence and the account records as execution evidence.
- **Manual and agent actions are mixed:** The same account can contain activity from another client or a person. When source attribution is unavailable, the audit says the cause is unknown rather than assigning it to the agent.
- **Open risk is omitted:** A positive realized fill result can sit beside a losing open position or resting order. Current positions and open orders remain in the report after the closed-trade calculation.
- **Funding and fees disappear:** Gross price change is not the account result. The audit includes trading fees and funding payments and says when a record is unavailable.

## Response contract

Report the account used, the exact instrument, the tools called, the controls that applied and the current order or position state. Separate a prepared order from a submitted order, and a submitted order from a fill. If no action was taken, say so directly.

## Sources

- [Hyperliquid account and order information endpoints](https://hyperliquid.gitbook.io/Hyperliquid-docs/for-developers/api/info-endpoint)
- [Hyperliquid historical data limits](https://hyperliquid.gitbook.io/hyperliquid-docs/historical-data)
- [Fensory MCP tools](https://fensory.com/mcp)

Product behavior and client permissions verified 2026-10-18.

Questions people ask

What does the Fensory Agent Trade Audit Skill install?

It downloads one SKILL.md file containing operating instructions, risk boundaries, the tool sequence and a response contract. It does not install the Fensory MCP server or create an account.