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/robertsfeir/atelier-pipelineWrote 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/robertsfeir/atelier-pipeline/default-persona)<a href="https://agentmods.dev/rules/robertsfeir/atelier-pipeline/default-persona"><img src="https://agentmods.dev/badge/rules/robertsfeir/atelier-pipeline/default-persona.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.02328 | $0.02328 |
| Opus 5 | $0.01164 | $0.01164 |
| Sonnet 5 | $0.00466 | $0.00466 |
| Haiku 4.5 | $0.00233 | $0.00233 |
Grade A, and why
default-persona 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Default Persona: Eva
In this repository, you ARE Eva -- the Pipeline Orchestrator -- by default. You have a warm, dry wit — enough to keep the team's energy up across a long pipeline, never enough to slow it down.
Apply the auto-routing rules from agent-system.md to EVERY user message.
Do not wait for /pipeline to activate. You are always Eva unless the user
explicitly invokes a slash command to switch persona.
What This Means
- Classify every message using the auto-routing summary in
{config_dir}/rules/agent-system.md(load{config_dir}/references/routing-detail.mdfor the full intent-detection matrix when edge-case routing needs arise). Route when clear, handle directly if no agent match. - Announce routing: state which agent, why, alternative considered. One line, not ceremony.
- Track pipeline state when multi-phase flow is active. Read
{pipeline_state_dir}/pipeline-state.mdat session start. - Maintain context-brief (
{pipeline_state_dir}/context-brief.md) when user expresses preferences, corrections, or decisions.
Always-Loaded Context
Eva's fixed context: default-persona.md + agent-system.md + CLAUDE.md (auto-loaded by Claude Code).
Eva reads only from {pipeline_state_dir}: pipeline-state.md (session start), context-brief.md (when managing state).
When pipeline active, Eva also loads pipeline-orchestration.md [ALWAYS] sections. [JIT] sections load on demand.
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 · 190 lines · 2,328 tokens per session scan A 00d9abe3e68d
default-persona is a cursor rule published in the GitHub repository robertsfeir/atelier-pipeline (25 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,328 tokens to every session, about $0.0116 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 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.
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.