tres-rollup-rules

tres-rollup-rules is a skill for Claude Code from anthropics/claude-plugins-community. It costs 226 tokens per session (6,288 once invoked), scanned A, original, Apache-2.0.

A finance tool for grouping repeated smaller transactions into one daily or monthly entry. TRES Finance is a system for managing financial transactions, and an ERP is business software that combines financial and operational records.

In plain words
What is it for?
Finding recurring transaction patterns, proposing or managing rollup rules, and preparing cleaner data for ERP integration.
Why use it?
It helps reduce clutter from repetitive transaction records while keeping the original transactions available for review.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin.

Part of the tres-finance-plugin plugin — 22 skills shipped together

Good fit Finding recurring transaction patterns, proposing or managing rollup rules, and preparing cleaner data for ERP integration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anthropics/claude-plugins-community/tres-rollup-rules
About the project

claude-plugins-community is a read-only mirror of a marketplace listing community-contributed plugins for Claude Cowork and Claude Code. It is for discovering and installing plugins that extend those Claude products, while submissions are handled through Anthropic’s separate review process. Catalogue add-ons represent plugins, skills, and integrations associated with this marketplace.

anthropics/claude-plugins-community · 3,663 stars · on GitHub

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 anthropics/claude-plugins-community --skill tres-rollup-rules
Clone the repo
git clone --depth 1 https://github.com/anthropics/claude-plugins-community

Made for: Claude Code.

Or install tres-finance-plugin, the plugin that ships this one along with the rest of its 22 skills.

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 tres-rollup-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/claude-plugins-community/tres-rollup-rules/github.svg)](https://agentmods.dev/skills/anthropics/claude-plugins-community/tres-rollup-rules)
Your own site
<a href="https://agentmods.dev/skills/anthropics/claude-plugins-community/tres-rollup-rules"><img src="https://agentmods.dev/badge/skills/anthropics/claude-plugins-community/tres-rollup-rules/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 tres-rollup-rules

Your own site · 80×15
<a href="https://agentmods.dev/skills/anthropics/claude-plugins-community/tres-rollup-rules"><img src="https://agentmods.dev/badge/skills/anthropics/claude-plugins-community/tres-rollup-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 226 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,288 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Anti-Refusal · line 216
    Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
    Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
  • high System Prompt Leakage · line 287
    Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
    Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
  • medium Excessive Agency · line 363
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.00226 $0.06288
Opus 5 $0.00113 $0.03144
Sonnet 5 $0.00045 $0.01258
Haiku 4.5 $0.00023 $0.00629

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

Security

Grade A, and why

tres-rollup-rules 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.

tres-finance-plugin/skills/tres-rollup-rules/SKILL.md · 510 lines

How it starts

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

TRES Finance — Rollup Rules

Analyze an organization's sub-transaction patterns, identify groups of repetitive transactions, and propose rollup rules that consolidate them into a single entry per interval for cleaner ERP integration. This is a data-driven discovery flow — you find the candidates from the data, validate each against real transactions, then present and create them.

A rollup rule is keyed on FOUR dimensions that together define exactly which sub-transactions it claims: internalAccount (wallet) + asset KEY + platform + balanceFactor (direction). Optional discriminating filters (fees, methodIds, subtxType, amount bounds, counterparties) narrow it further. Everything you discover and propose must map onto this shape — see the Rule Field Reference at the bottom.

A rollup is non-destructive: the original raw sub-transactions are always preserved and visible in the Rollup Breakdown report.

All GraphQL runs through the TRES Finance MCP connector (execute tool; validate with validate_query first when unsure). All variable keys and nested input fields MUST use camelCase (e.g. internalAccountId, balanceFactor), NEVER snake_case.


Routing

  • "Suggest / create / propose rollup rules", "too many transactions", "roll up X" → run the full discovery pipeline (Steps 0–6 below). This is the main flow.
  • "Show / list my rollup rules" → Section A (List existing rules), then stop.
  • "Delete a rollup rule" → Section C (Delete rules).
  • "Review this specific rule" / "what would this rule match" → hand off to the tres-rollup-review skill.

Step 0 — Confirm Scope

Establish scope with the user, but keep it light — only the analysis is scoped, the rules themselves are usually open-ended.

Analysis window (OPTIONAL)

A period only narrows the discovery queries so you look at recent, representative activity. It is NOT required, and it is NOT the rule's date range.

  • "Q1 2025" → start: 2025-01-01T00:00:00Z, end: 2025-03-31T23:59:59Z
  • "last 3 months" → compute from today

Read the full file on GitHub · 510 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 510 lines · 226 tokens per session scan A a30935122269

Subscribe to this mod's changes

tres-rollup-rules is a skill published in the GitHub repository anthropics/claude-plugins-community (3,663 stars, last pushed 14d ago), licensed Apache-2.0. It adds 226 tokens to every session and 6,288 once invoked, about $0.0011 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-30.

Related

Other skills, from other repositories