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 bpais88/dynt-agent-skills --skill dynt-transaction-cleanupgit clone --depth 1 https://github.com/bpais88/dynt-agent-skillsWrote 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/bpais88/dynt-agent-skills/dynt-transaction-cleanup)<a href="https://agentmods.dev/skills/bpais88/dynt-agent-skills/dynt-transaction-cleanup"><img src="https://agentmods.dev/badge/skills/bpais88/dynt-agent-skills/dynt-transaction-cleanup/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/bpais88/dynt-agent-skills/dynt-transaction-cleanup"><img src="https://agentmods.dev/badge/skills/bpais88/dynt-agent-skills/dynt-transaction-cleanup.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.00072 | $0.00448 |
| Opus 5 | $0.00036 | $0.00224 |
| Sonnet 5 | $0.00014 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
dynt-transaction-cleanup 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 12d 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.
What it actually says
FIRST: read the parent dynt skill for connection, safety rules and tool families.
Transaction cleanup
Outcome: the review queue is smaller, and every change was previewed and approved.
1. Size the queue
get_transaction_summary→ "needs review" count.get_account_overview→ merchant coverage percentage.list_transactionswithstatus: "needs_review", paginated, to sample the queue: show 10 examples (date · merchant/raw description · amount).
2. Preview what the suggestions would do
Dynt keeps pending category and merchant suggestions per transaction. Explain both, and that the bulk tools apply all pending suggestions of that kind — there is no partial accept through MCP. If the user wants to exclude items, stop: that must be done in the Dynt app.
Show: how many transactions each bulk action would touch (from the sample and counts), and 5 representative before → after lines.
3. Apply (write — confirm each action separately)
accept_all_category_suggestions→ returns the number updated.accept_all_merchant_suggestions→ returns the number updated.
Report the counts and re-run get_transaction_summary to show the new
"needs review" figure.
Gotchas
- Requires
write; a viewer or read-only credential can only report. - Suggestions are Dynt's; do not invent categories or merchants yourself.
- Never chain the two accepts without a separate yes for each.
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.
- 12d ago First seen · 51 lines · 72 tokens per session scan A 4623f3bc265d
dynt-transaction-cleanup is a skill published in the GitHub repository bpais88/dynt-agent-skills (0 stars, last pushed 11d ago), licensed MIT. It adds 72 tokens to every session and 448 once invoked, about $0.0004 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.
Other skills, from other repositories
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
furusato
A Japanese hometown-tax donation manager for furusato nozei, a system where donations to municipalities can qualify for an income-tax or local-tax deduction. It reads donation receipts, stores donation records, and calculates deduction limits.
reading-receipt
An image-reading workflow for extracting structured information from receipts, invoices, and hometown-tax donation certificates. It can first extract text from PDFs and otherwise read their images.