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 agentmods add rules/altaidevorg/rules-for-ai/filters___filterlib__git clone --depth 1 https://github.com/altaidevorg/rules-for-aiWrote 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/rules/altaidevorg/rules-for-ai/filters___filterlib__)<a href="https://agentmods.dev/rules/altaidevorg/rules-for-ai/filters___filterlib__"><img src="https://agentmods.dev/badge/rules/altaidevorg/rules-for-ai/filters___filterlib__.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.04023 |
| Opus 5 | $0.00015 | $0.02011 |
| Sonnet 5 | $0.00006 | $0.00805 |
| Haiku 4.5 | $0.00003 | $0.00402 |
Grade A, and why
filters___filterlib__ 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 4d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapter 4: Filters (filterlib)
In the previous chapters, we learned how nnx.Module defines network components, how nnx.Variable / nnx.VariableState represents their state, and how nnx.Rngs manages randomness. Models often contain diverse state elements (parameters, batch statistics, caches, RNG state, etc.) nested within complex structures. When working with these models, especially when using the NNX Functional API (split/merge/state/update/graphdef) or applying NNX Lifted Transforms (jit, grad, vmap, scan, etc.), we frequently need to select specific subsets of this state. This is where Filters come in.
Motivation: Targeted State Manipulation
Imagine you want to:
- Apply an optimizer update only to the learnable parameters (
nnx.Param) and not the batch statistics (nnx.BatchStat). - Extract only the batch statistics to update them manually during inference.
- Specify which parts of the state should be differentiated using
nnx.grad. - Define how different state components should be handled (mapped, broadcasted, carried) in
nnx.vmapornnx.scan. - Remove temporary state like intermediate activations (
nnx.Intermediate) after a forward pass.
Manually traversing the nested State pytree and checking types or names for each VariableState would be verbose and error-prone. Filters provide a concise and powerful declarative language for specifying these selections.
Central Use Case: Separating Parameters and Batch Statistics
A common task is separating the parameters that need gradients from the batch statistics that are updated differently. Filters make this straightforward using nnx.split.
import jax
import jax.numpy as jnp
from flax import nnx
class MyModel(nnx.Module):
def __init__(self, *, rngs: nnx.Rngs):
self.layer1 = nnx.Linear(10, 20, rngs=rngs)
self.bn = nnx.BatchNorm(20, use_running_average=False, rngs=rngs)
self.layer2 = nnx.Linear(20, 5, rngs=rngs)
def __call__(self, x):
x = self.layer1(x)
x = self.bn(x)
x = nnx.relu(x)
x = self.layer2(x)
return x
model = MyModel(rngs=nnx.Rngs(0))
# Use Variable types as filters in nnx.split
graphdef, params_state, bn_state, other_state = nnx.split(
model,
nnx.Param, # Filter 1: Select all nnx.Param variables
nnx.BatchStat, # Filter 2: Select all nnx.BatchStat variables
... # Filter 3: Select everything else (Ellipsis or True)
)
print("--- Parameters (nnx.Param) ---")
# params_state contains only VariableState objects whose type is nnx.Param
print(params_state)
print("\n--- Batch Statistics (nnx.BatchStat) ---")
# bn_state contains only VariableState objects whose type is nnx.BatchStat
print(bn_state)
print("\n--- Other State (e.g., RngState for BatchNorm) ---")
# other_state contains the rest (e.g., RngState from BatchNorm)
print(other_state)
# Reconstruct the model
model_merged = nnx.merge(graphdef, params_state, bn_state, other_state)
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.
- 4d ago First seen · 309 lines · 29 tokens per session scan A 792bda3a9d9c
filters___filterlib__ is a cursor rule published in the GitHub repository altaidevorg/rules-for-ai (2 stars, last pushed 1y ago), licensed MIT. It adds 29 tokens to every session and 4,023 once invoked, about $0.0001 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.