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/AmanKtyr/TailorWrote 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/amanktyr/tailor/tailor)<a href="https://agentmods.dev/rules/amanktyr/tailor/tailor"><img src="https://agentmods.dev/badge/rules/amanktyr/tailor/tailor/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/amanktyr/tailor/tailor"><img src="https://agentmods.dev/badge/rules/amanktyr/tailor/tailor.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.00714 | $0.00714 |
| Opus 5.5 | $0.00286 | $0.00286 |
| Sonnet 5.5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
tailor 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 92% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidance (Powered by Tailor)
This repository uses Tailor for project intelligence, Spec-Driven Development, and Reuse-First engineering discipline.
Non-Negotiable Directives
1. Cold-Start & Project Memory Hierarchy
- Always consult
.ai/CONSTITUTION.mdand.ai/INDEX.mdfirst before planning or making non-trivial modifications. - Cold-Start Fallback: If the
.ai/directory does not exist yet, do NOT invent arbitrary conventions. Inspectpackage.json(or workspace manifests) and active source files directly to determine established patterns, and suggest runningnpx @amanktyr/tailor initto establish project memory.
2. Mandatory Guardrail: Zero Unrequested Styling & Redesign
- STRICTLY PROHIBITED: NEVER add, alter, or inject CSS, styling frameworks, inline styles, gradients, glassmorphism, or animations unless the user explicitly requested visual or styling changes.
- When working on logic, bugfixes, refactoring, or state management: preserve existing visual markup and styling tokens untouched.
- When writing UI components: strictly reuse existing design tokens, components, and CSS classes from the codebase or
.ai/UI.md. Never invent new arbitrary classes, hex colors, or custom styling rules. - If the project has no styling system and no styling is requested, output clean, unstyled semantic HTML.
3. Mandatory Guardrail: Zero Bloat & Minimal Diff Discipline (Anti-Slop)
- Implement only the minimal code required to satisfy the user's specific request.
- NO speculative abstractions: Do not create premature wrapper classes, generic factories, or speculative interfaces for one-off operations.
- NO dummy/mock data: Never add mock datasets, fake user lists, or placeholder fixtures in production code.
- NO filler comments: Never write redundant explanatory comments (e.g.
// Here we define the function) that state the obvious. Only document why non-obvious business logic or security decisions exist.
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.
- 1mo ago Changed · +25 lines · +504 tokens per session 8a64b0f60cb3
- 1mo ago First seen · 16 lines · 210 tokens per session scan A d76b717ab88b
tailor is a cursor rule published in the GitHub repository AmanKtyr/Tailor (6 stars, last pushed 11d ago), licensed MIT. It adds 714 tokens to every session, about $0.0029 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-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-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).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.