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 skills/pekral/cursor-rules/blueprintnpx skills add pekral/cursor-rules --skill blueprintgit clone --depth 1 https://github.com/pekral/cursor-rulesWrote 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/skills/pekral/cursor-rules/blueprint)<a href="https://agentmods.dev/skills/pekral/cursor-rules/blueprint"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/blueprint.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.00070 | $0.01588 |
| Opus 5 | $0.00035 | $0.00794 |
| Sonnet 5 | $0.00014 | $0.00318 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
blueprint 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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blueprint
Constraints
- Apply
@rules/git/general.mdc— branch, commit, and PR conventions below come from it. - Apply
@rules/compound-engineering/general.mdc— the plan is durable memory the next agent reuses, not throwaway prose. - Apply
@rules/compound-engineering/general.mdcAssign the most relevant existing label when creating a tracker issue for any tracker issue this plan creates or hands off to@skills/create-issues-from-text/SKILL.mdto create. - Apply
@rules/laravel/architecture.mdcwhen the project usespekral/arch-app-services, so each step lands in the correct layer. - Plan only. Do not implement, commit, or push any step.
- Output Markdown only. English only.
- Every step must be one pull request: independently reviewable and mergeable on its own.
- Break the objective into 3-12 steps. Fewer means it likely fits one PR; more means the objective is too broad and should be split first.
- Each step must be executable cold by
@skills/resolve-issue/SKILL.mdor a fresh agent with no prior context. - Do not invent dependencies on tooling that may be absent. Degrade gracefully when GitHub CLI (
gh) is missing.
Use when
- An objective clearly exceeds one pull request (a migration, a multi-layer feature, a cross-cutting refactor).
- Work will span multiple sessions or multiple agents and needs a sequenced, resumable plan.
- You need to know which parts can run in parallel and which must be sequential before starting.
Do not use for single-PR tasks (use @skills/analyze-problem/SKILL.md or @skills/resolve-issue/SKILL.md), for splitting an objective into tracker issues without a dependency graph (use @skills/create-issues-from-text/SKILL.md), or when the user wants one high-leverage suggestion (@skills/smartest-project-addition/SKILL.md / @skills/product-capability/SKILL.md).
Execution
Run the five phases in order. Do not register a plan that has not passed Review.
- Research — Establish ground truth before planning.
- Read the actual code, layers, and conventions the objective will touch. Per
@rules/compound-engineering/general.mdc, find the existing part of the system the work extends before inventing a new abstraction. - Walk
git log/git blameover the affected area to learn how it evolved and what was already tried or reverted. - Detect the git baseline: confirm the repo, the default branch (
master), and whetherghis available (gh auth status). Record the result; it drives the PR template in Output. - For an unfamiliar pattern, library, or security-sensitive surface, consult current authoritative references and cite them.
- Read the actual code, layers, and conventions the objective will touch. Per
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.
- 3d ago First seen · 86 lines · 70 tokens per session scan A 5911d743ad80
blueprint is a skill published in the GitHub repository pekral/cursor-rules (6 stars, last pushed 9d ago), licensed MIT. It adds 70 tokens to every session and 1,588 once invoked, about $0.0003 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 skills, from other repositories
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
parse-table
Parse table definition to extract module name, model name, table name, and field definitions. First step of CRUD generation.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.
pulse-development
Handles Laravel Pulse setup, configuration, and custom card development. Activates when installing Pulse; configuring the dashboard or authorization gate; setting up recorders and filtering; building custom Livewire cards; optimizing with Redis ingest or sampling; or when the user mentions /pulse, pulse:check…
module:assistant
Add an AI assistant chat panel to any Laravel project — with tool calling, streaming, and MCP support.
migrate-spec
Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers YAML layout (state.yaml, release-plan.yaml, epics/, requirements/, plans/, ADRs). Use when migrating foreign spec docs.