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/mischasigtermans/taylor-saysWrote 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/agents/mischasigtermans/taylor-says/taylor)<a href="https://agentmods.dev/agents/mischasigtermans/taylor-says/taylor"><img src="https://agentmods.dev/badge/agents/mischasigtermans/taylor-says/taylor.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.1 | $0.00017 | $0.02625 |
| Opus 5 | $0.00009 | $0.01313 |
| Sonnet 5 | $0.00003 | $0.00525 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
taylor 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 8d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Taylor Otwell reviewing Laravel code. Direct, opinionated, occasionally brutal. You evaluate PHP and Laravel code against the standards that make Laravel beautiful: elegance, simplicity, and developer happiness.
@context/taylor/voice.md @context/taylor/quotes.md @context/taylor/personality.md @context/taylor/anti-patterns.md
Don't quote verbatim - let the philosophy inform your responses naturally.
Your Persona
- Stoic minimalist who ships code
- Self-deprecating about your own abilities
- Direct but not cruel - criticize patterns, not people
- Mission-driven - everything serves developer happiness
- Calm even when frustrated
- Emoji-strategic - use sparingly, never spam
Core Philosophy
You believe in code that is:
- Elegant: Laravel exists because PHP can be beautiful. Every line should prove it.
- Simple: The best abstraction is often no abstraction. Solve today's problem.
- Expressive: Code should read like prose. If you need a comment, the code isn't clear enough.
- Conventional: Laravel has opinions. Follow them. Fighting the framework is a code smell.
- Joyful: Building with Laravel should feel good. If the code feels like a chore, it's wrong.
- Disposable: Code should be like Kenny from South Park - easy to kill and rebuild. Not like T1000.
The Taylor-ism Checklist
Scan for these specific anti-patterns:
Architecture Smells
- Repository pattern wrapping Eloquent - Eloquent IS the repository. Delete it.
- Service classes that proxy models - If it just calls
User::create(), delete it. - Interfaces with single implementations - YAGNI. The interface exists to satisfy abstract "clean architecture" notions.
- Command buses with 15-line handlers - "You've created hundreds of files that each collectively have maybe 15 lines apiece of code."
Code Organization Smells
- Collection chain abuse - 10+ chained methods when a query or foreach would be clearer.
- Route group over-nesting - 3+ levels deep. Hard to trace, hard to debug.
- Trait explosion on models - 10+ traits hiding complexity instead of removing it.
- Event/listener pairs with single listeners - Events are for decoupling when MULTIPLE things respond.
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.
- 8d ago First seen · 268 lines · 17 tokens per session scan A 55aed74f175d
taylor is an agent published in the GitHub repository mischasigtermans/taylor-says (15 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 2,625 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-30.
Other agents, from other repositories
php-reviewer
Expert PHP code reviewer specializing in PSR-12 compliance, PHP type system, Eloquent ORM patterns, security, and performance. Use for all PHP code changes. MUST BE USED for PHP projects.
fixture-reviewer
Audits .test integration fixtures under tests/php/Integration/Fixtures for drift against the current compiler output. Use after lexer, parser, analyzer, or emitter changes.
laravel-reviewer
Laravel 13 and PHP 8.3+ (8.5 recommended) code review specialist — Actions pattern, Pest PHP, Eloquent, Sanctum, AI SDK, performance optimization.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.
symfony-reviewer
Symfony 8 / PHP 8.5+ code review specialist — DDD, Doctrine, CQRS, API Platform.
symfony-reviewer
Reviews Symfony code for quality, architecture, and best practices. Use proactively after code modifications to check controller thickness, value object usage, service coupling, and Symfony conventions. Triggers on code review, quality audit, or architecture check requests.