transaction-reporting

transaction-reporting is a skill for Claude Code, Codex from newline53/newline-mcp-server. It costs 68 tokens per session (747 once invoked), scanned A, original, Apache-2.0.

A transaction-reporting workflow for the Newline MCP server, which provides access to payment and account records. It gathers transaction histories, event timelines, account evidence, and customer activity for summaries or audits.

In plain words
What is it for?
Use it to list or inspect transactions, filter by customer or account, track payment status over time, and summarize balances, transfers, and related events.
Why use it?
It defines which identifiers and transaction fields to collect, making financial activity easier to investigate and report consistently.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; mentions Codex.

Good fit Use it to list or inspect transactions, filter by customer or account, track payment status over time, and summarize balances, transfers, and related events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/newline53/newline-mcp-server/transaction-reporting
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 newline53/newline-mcp-server --skill transaction-reporting
Clone the repo
git clone --depth 1 https://github.com/newline53/newline-mcp-server

Made for: Claude Code, Codex.

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 transaction-reporting

README.md
[![agentmods](https://agentmods.dev/badge/skills/newline53/newline-mcp-server/transaction-reporting/github.svg)](https://agentmods.dev/skills/newline53/newline-mcp-server/transaction-reporting)
Your own site
<a href="https://agentmods.dev/skills/newline53/newline-mcp-server/transaction-reporting"><img src="https://agentmods.dev/badge/skills/newline53/newline-mcp-server/transaction-reporting/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 transaction-reporting

Your own site · 80×15
<a href="https://agentmods.dev/skills/newline53/newline-mcp-server/transaction-reporting"><img src="https://agentmods.dev/badge/skills/newline53/newline-mcp-server/transaction-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 747 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.
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.00068 $0.00747
Opus 5 $0.00034 $0.00374
Sonnet 5 $0.00014 $0.00149
Haiku 4.5 $0.00007 $0.00075

Measured 10d ago against content hash ddd2b6807826, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

transaction-reporting 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 10d 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/transaction-reporting/SKILL.md · 136 lines

How it starts

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

Transaction Reporting

Use this skill to retrieve, monitor, and summarise transaction activity. It is broader than investigate-transfer and works well for reporting, audit, and dashboard-style questions.

Step 1 — Define the Reporting Scope

Determine the narrowest useful anchor:

  • customer UID
  • synthetic account UID
  • transfer UID
  • transaction UID
  • date range or recent activity window

Then choose the appropriate list or get tool.

Step 2 — Retrieve Transactions

For broad history:

list-transactions  (filter by uid, external_uid, synthetic_account_uid, customer_uid, transaction_type, status, transfer_uid, limit, offset, sort)

For one specific record:

get-transaction  uid=<transaction_uid>

Capture:

  • uid, external_uid
  • transaction_type
  • status
  • amount, currency
  • synthetic_account_uid
  • customer_uid
  • transfer_uid
  • custodial_account_uid
  • balance_after
  • timestamps and description

Step 3 — Monitor Status Over Time

If the user asks whether something has completed, use repeated reads of:

get-transaction  uid=<transaction_uid>

General timing guidance:

  • instant payment: seconds
  • wire: same day to next business day
  • ACH: often 1–2 business days

If still queued or pending, report that processing is ongoing rather than assuming failure.

Step 4 — Pull the Event Timeline

list-transaction-events

Identify events for the relevant transaction and build a timeline of status changes. If you need more detail for one event:

get-transaction-event  uid=<transaction_event_uid>

Use this for audit trails and failure analysis.

Step 5 — Connect Transactions Back to Transfers

If a transaction has a transfer_uid, inspect the parent transfer:

get-newline-transfer  uid=<transfer_uid>

If you need to find recent transfers first:

list-newline-transfers

This helps explain direction, counterparties, and rail-specific fields.

Step 6 — Check Posting Evidence on Accounts

Read the full file on GitHub · 136 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. 10d ago First seen · 136 lines · 68 tokens per session scan A ddd2b6807826

Subscribe to this mod's changes

transaction-reporting is a skill published in the GitHub repository newline53/newline-mcp-server (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 747 once invoked, about $0.0003 per session on Opus 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-31.

Related

Other skills, from other repositories

surf

Surf (asksurf.ai) is RETIRED on BlockRun and the blockrunsurf tool was REMOVED in 0.49.0 — the gateway has answered every /v1/surf/ path with HTTP 410 endpointretired since 2026-09-06. Use this skill to route a former Surf question (on-chain SQL, wallet labels and net worth, CEX order books, social mindshare, news) to…

BlockRunAI/blockrun-mcp · 110 tokens

scanner-pmcc

Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.

staskh/trading_skills · 63 tokens

ib-collar

Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.

staskh/trading_skills · 30 tokens

ib-portfolio-action-report

Generate a comprehensive portfolio action report with earnings dates and risk assessment. Use when user asks for portfolio review, action items, earnings risk, or position management across IB accounts. Requires TWS or IB Gateway running locally.

staskh/trading_skills · 49 tokens

ib-trades-history

Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.

staskh/trading_skills · 59 tokens

report-stock

Generate comprehensive stock analysis report (PDF or markdown) with trend, PMCC, and fundamental analysis.

staskh/trading_skills · 22 tokens