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.
git clone --depth 1 https://github.com/julien777z/agent-sync-actionWrote 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/julien777z/agent-sync-action/pydantic)<a href="https://agentmods.dev/rules/julien777z/agent-sync-action/pydantic"><img src="https://agentmods.dev/badge/rules/julien777z/agent-sync-action/pydantic/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/rules/julien777z/agent-sync-action/pydantic"><img src="https://agentmods.dev/badge/rules/julien777z/agent-sync-action/pydantic.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.00000 | $0.01044 |
| Opus 5.5 | $0.00000 | $0.00418 |
| Sonnet 5.5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
pydantic 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pydantic Rules
Model Design
-
Never use
@dataclassdecorator fromdataclassesmodule. -
Use Pydantic
BaseModelfor all class definitions that hold data. -
Do not use
NamedTuplefor application or script data models; use an explicitBaseModelsubclass instead. -
Pydantic provides validation, serialization, and type coercion out of the box.
-
Expose zero-argument boolean accessors as
@propertyinstead of methods when they describe model state or capability. -
Prefer property names such as
can_access_xyzovercan_access_xyz().
class AccessPolicy(BaseModel):
role: str
@property
def can_access_admin(self) -> bool:
return self.role == "admin"
policy = AccessPolicy(role="member")
if not policy.can_access_admin:
raise PermissionError("Admin access required")
-
Never use
Protocolfor data models that hold data. -
Use
Protocolonly for structural typing of interfaces (callbacks, duck typing). -
Use
Selfreturn type for class methods.
Validation and Configuration
- Use
model_config = ConfigDict(...)for model configuration. - Use
model_dump()instead of deprecateddict(). - Use
model_validatordecorator for custom validation. - Do not add
field_validatorormodel_validatorjust to coerce enum strings that should be represented by the enum itself; update the enum values to match the real contract instead. - Do not define
__init__onBaseModelsubclasses; use fields, validators,model_post_init, or factory/class methods instead. - Never use
pydantic.create_model; define an explicitBaseModelsubclass instead. Ifcreate_modelfeels necessary, the design is probably too dynamic or too clever; refactor toward a named model class.
from enum import StrEnum
from pydantic import BaseModel, field_validator
class ShirtSize(StrEnum):
SMALL = "small"
LARGE = "large"
# Bad: validator added only to paper over the wrong enum values
class TShirtOrderBad(BaseModel):
size: ShirtSize
@field_validator("size", mode="before")
@classmethod
def validate_size(cls, value: str) -> str:
return value.upper()
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.
- 5d ago Changed · +117 lines · -9 tokens per session 1abbea915b40
- 2mo ago First seen · 1 lines · 9 tokens per session scan A 1db166dd622d
pydantic is a cursor rule published in the GitHub repository julien777z/agent-sync-action (9 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,044 tokens. 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).