filter-explain

filter-explain is a skill for Claude Code from mindbox-cloud/agent-skills. It costs 145 tokens per session (1,522 once invoked), scanned A, original, MIT.

A skill for explaining a saved customer or object filter in plain language. CDP means a customer data platform, and a filter is a set of conditions used to select records.

In plain words
What is it for?
Explaining filter conditions, values, selected records, and missing connections using the connected project.
Why use it?
It helps people understand which records a filter selects without manually translating its JSON conditions into business terms.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the mindbox plugin — 5 skills shipped together

Good fit Explaining filter conditions, values, selected records, and missing connections using the connected project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mindbox-cloud/agent-skills/filter-explain
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 mindbox-cloud/agent-skills --skill filter-explain
Clone the repo
git clone --depth 1 https://github.com/mindbox-cloud/agent-skills

Made for: Claude Code.

Or install mindbox, the plugin that ships this one along with the rest of its 5 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 filter-explain

README.md
[![agentmods](https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/filter-explain/github.svg)](https://agentmods.dev/skills/mindbox-cloud/agent-skills/filter-explain)
Your own site
<a href="https://agentmods.dev/skills/mindbox-cloud/agent-skills/filter-explain"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/filter-explain/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 filter-explain

Your own site · 80×15
<a href="https://agentmods.dev/skills/mindbox-cloud/agent-skills/filter-explain"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/filter-explain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 145 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,522 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.00145 $0.01522
Opus 5.5 $0.00058 $0.00609
Sonnet 5.5 $0.00029 $0.00304
Haiku 4.5 $0.00015 $0.00152

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

Security

Grade A, and why

filter-explain 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.

plugins/mindbox/skills/filter-explain/SKILL.md · 123 lines

How it starts

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

Filter explain

Choose the project and input

Find the connected server's filter_* tools. Explain a missing connection. Keep calls on that server: names and IDs identify records only within the project it serves.

Use the complete original filter JSON. A filtered-list URL cannot be imported, and these tools do not fetch saved filters by name. If only a link or an unseen filter is supplied, ask for its JSON. For a successful build already in this conversation, reuse its confirmed finalSql and selected records instead of converting it again.

Freshly read the connected server's maintained, up-to-date entry point: filter_wiki_read with paths = ["README.md"].

Use its navigation and current tool guidance. Reuse pages within this explanation. Examples below name a tool and the arguments that carry the request; fill in the rest from the schema the server exposes. Use the actual input and returned paths. Tool names may have a server prefix.

1. Convert the original JSON to SQL

Pass the complete JSON unchanged to filter_json_to_sql as its filterJson object — for example this filter, customers aged 30 and over:

{
  "entityType": "User",
  "filterFactory": "and",
  "innerConditions": [{
    "entityType": "User",
    "filterFactory": "age",
    "value": {"mode": "concrete", "value": {"range": {"from": "30", "to": ""}, "unit": "Years"}}
  }]
}

Read the returned sql, selected records and warnings. The tool already attempts to resolve catalogue IDs to names; do not repeat successful lookups. status: read means the JSON was read, not that the platform has accepted the filter. unlabelled means some values remain unnamed; unsupported or UNSUPPORTED_FILTER(...) marks conditions the conversion cannot explain. Keep the original JSON and these gaps visible in your reasoning. Do not reconstruct a simpler filter to make them disappear.

2. Read the meaning and resolve remaining labels

Identify the root, fields, relations, operators and business concepts in the SQL. Search the wiki for each distinct concept whose meaning or limitations you need to establish, combining related terms in a regex and reusing relevant pages already read:

Read the full file on GitHub · 123 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. 12d ago First seen · 123 lines · 145 tokens per session scan A ff672ad0ee2d

Subscribe to this mod's changes

filter-explain is a skill published in the GitHub repository mindbox-cloud/agent-skills (6 stars, last pushed 9d ago), licensed MIT. It adds 145 tokens to every session and 1,522 once invoked, about $0.0006 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-10-01.

Related

Other skills, from other repositories

prove-the-gates

Audit the repository's own checks — for each test, gate and CI script, establish what it guards, whether anything still runs it, and whether it actually fails when you break what it protects. Use when the user says "prove the gates", "are our tests real", "audit the test suite", "which checks are fake", "תוכיח את…

orenluxy/fable-method · 127 tokens

implementation-notes

Maintain an IMPLEMENTATIONNOTES.md decision log during any multi-step implementation session. Use this in EVERY session that involves writing or modifying code across more than one file, or any session expected to run longer than a few tool calls. Records decisions, deviations from plan, and open questions so nothing…

orenluxy/fable-method · 66 tokens

full-audit

Audit a whole repository in one pass — dispatch every applicable audit lane in parallel, prove the repo's own gates fail when they should, and return one evidence-backed report ranked by severity. Use when the user says "full audit", "audit this repo", "check the whole codebase", "תעשה אודיט מלא", "אודיט לריפו"…

orenluxy/fable-method · 116 tokens

fable-method

The routing logic of the Fable Method - decides which unknowns-discovery technique (blindspot-pass, interview-me, prototype-first, implementation-notes, merge-quiz) applies to the current task, and which to skip. Consult this at the START of any non-trivial task, or when the user says "fable", "the method", "how…

orenluxy/fable-method · 92 tokens

blindspot-pass

Run a blindspot scan to surface the user's unknown unknowns BEFORE implementing a task. Use this whenever the user starts a non-trivial task in a domain they say (or appear) to be unfamiliar with, whenever they say "blindspot", "unknowns", "what am I missing", "before we start", or when a request is vague enough that…

orenluxy/fable-method · 95 tokens

convergence-guard

Stop-loss discipline for implementation sessions - detect fix-loops and runaway token burn, and stop to replan instead of patching. Consult during any debugging or implementation session, especially when tests keep failing, the same file keeps being edited, or the user mentions stoploss, token budget, fix loops, or…

orenluxy/fable-method · 74 tokens