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.
npx skills add newline53/newline-mcp-server --skill investigate-transfergit clone --depth 1 https://github.com/newline53/newline-mcp-serverWrote 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.
[](https://agentmods.dev/skills/newline53/newline-mcp-server/investigate-transfer)<a href="https://agentmods.dev/skills/newline53/newline-mcp-server/investigate-transfer"><img src="https://agentmods.dev/badge/skills/newline53/newline-mcp-server/investigate-transfer/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.
<a href="https://agentmods.dev/skills/newline53/newline-mcp-server/investigate-transfer"><img src="https://agentmods.dev/badge/skills/newline53/newline-mcp-server/investigate-transfer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.00610 |
| Opus 5.5 | $0.00021 | $0.00244 |
| Sonnet 5.5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
investigate-transfer 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate Transfer
Full drill-down workflow for understanding the state and history of a transfer.
Step 1 — Get the Transfer
If you have the transfer UID directly:
get-newline-transfer uid=<transfer_uid>
If you need to find it first:
list-newline-transfers
Note from the transfer response:
status— current state of the transfertransaction_uids— list of associated transaction UIDssource_synthetic_account_uidanddestination_synthetic_account_uidinitiating_customer_uidanddestination_customer_uidusd_transfer_amountach,wire, orinstant_paymentblock — identifies the transfer type
Step 2 — Inspect Each Transaction
For every UID in transaction_uids, fetch the full transaction:
get-transaction uid=<transaction_uid>
Note for each transaction:
status— e.g.settled,pending,failedtransaction_typeamountandcurrencybalance_after— running balance on the synthetic account after this entrycustodial_account_uid— the underlying custodial account
Step 3 — Check Transaction Events
Transaction events capture lifecycle state changes (initiated, settled, failed, returned, etc.):
list-transaction-events
Look for events whose transaction_uid matches any of the transactions found in Step 2.
Pay attention to event_type and status for any failure or return indicators.
Step 4 — Check for Returns
list-returns
Look for returns where original_transaction_uid matches a transaction from Step 2.
If a return is found:
- Note
return_reason,amount,status, andprocessed_at - See the
return-resolutionskill for next steps
Step 5 — Check the Combined Transfer View (Optional)
If the transfer is part of a batch or grouped operation:
list-combined-transfers
Look for a combined transfer whose transfer_uids includes the transfer UID from Step 1.
The combined transfer shows total_amount and overall status across all constituent transfers.
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.
- 2mo ago First seen · 89 lines · 53 tokens per session scan A f989220e6597
investigate-transfer is a skill published in the GitHub repository newline53/newline-mcp-server (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 610 once invoked, about $0.0002 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-31.
investigate-transfer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| investigate-transfernewline53/newline-mcp-server | Skill | 2 | 6mo ago | Apache-2.0 | A | 53 | Claude Code, Codex |
| n8n-error-handlingczlonkowski/n8n-mcp | Skill | 23k | today | MIT | A | 128 | Claude Code, Codex |
| ib-collarstaskh/trading_skills | Skill | 404 | 3d ago | MIT | A | 30 | Claude Code |
| ib-report-delta-adjusted-notional-exposurestaskh/trading_skills | Skill | 404 | 3d ago | MIT | A | 58 | Claude Code |
| report-stockstaskh/trading_skills | Skill | 404 | 3d ago | MIT | A | 22 | Claude Code |
| ib-portfoliostaskh/trading_skills | Skill | 404 | 3d ago | MIT | A | 38 | Claude Code |
| memorix-troubleshootingAVIDS2/memorix | Skill | 915 | yesterday | Apache-2.0 | A | 36 | Claude Code |