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 mindbox-cloud/agent-skills --skill filter-buildgit clone --depth 1 https://github.com/mindbox-cloud/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/mindbox-cloud/agent-skills/filter-build)<a href="https://agentmods.dev/skills/mindbox-cloud/agent-skills/filter-build"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/filter-build/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/mindbox-cloud/agent-skills/filter-build"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/filter-build.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.00175 | $0.03137 |
| Opus 5.5 | $0.00070 | $0.01255 |
| Sonnet 5.5 | $0.00035 | $0.00627 |
| Haiku 4.5 | $0.00017 | $0.00314 |
Grade A, and why
filter-build 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filter build
Find the connected server's filter_* tools and feedback. Explain a missing connection.
Keep all calls on that server: catalogue IDs belong to the project it serves.
Examples below are independent and use synthetic requests. Each names a tool and the arguments that carry the request; fill in the rest from the schema the server exposes. Use the actual request, editor and returned records. Tool names may have a server prefix.
1. Read the current entry point
At the start of every build or edit, freshly read the connected server's root README, even if you read it in an earlier task:
Read it with filter_wiki_read, paths = ["README.md"].
This is the maintained, up-to-date entry point. Use its current navigation and tool guidance alongside the workflow below. Reuse pages within this build; follow returned paths instead of reconstructing filenames. Do not preload the full syntax and build guides.
For an edit, retain the complete set of existing conditions, plus the requested changes.
Reuse a confirmed finalSql and selected records from this conversation. Otherwise call
filter_json_to_sql with the complete original JSON; keep its selected records and inspect
unlabelled and unsupported. A list URL cannot be imported by these tools: ask for JSON
if the filter is not already in context. Do not silently drop an unreadable condition.
2. Choose the root and editor
If either the root or property set is unknown, read the root catalogue:
filter_wiki_read with paths = ["root/README.md"].
Choose the root by what one result row represents: customers, products, orders or another
listed object. Objects mentioned in conditions may be related to that root. Preserve any
root and property set supplied by the caller. For a standalone list, use the root's Default
editor; for an embedded mechanic, use its required editor. Ask if the destination is unclear
and the choice changes what can be expressed.
Open the chosen editor page to learn its available fields, relations and restrictions. If both values were supplied, go directly to that page after step 1. API identifiers and wiki paths have different casing:
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 · 264 lines · 175 tokens per session scan A 2ec81f4859b5
filter-build is a skill published in the GitHub repository mindbox-cloud/agent-skills (6 stars, last pushed 9d ago), licensed MIT. It adds 175 tokens to every session and 3,137 once invoked, about $0.0007 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.
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", "תוכיח את…
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…
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", "תעשה אודיט מלא", "אודיט לריפו"…
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…
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…
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…