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 skills add pekral/cursor-rules --skill understand-propose-implement-verifygit 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/understand-propose-implement-verify)<a href="https://agentmods.dev/skills/pekral/cursor-rules/understand-propose-implement-verify"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/understand-propose-implement-verify/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/skills/pekral/cursor-rules/understand-propose-implement-verify"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/understand-propose-implement-verify.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.00026 | $0.00459 |
| Opus 5.5 | $0.00010 | $0.00184 |
| Sonnet 5.5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
understand-propose-implement-verify 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.
What it actually says
Constraints
- Apply
@rules/php/core-standards.mdconly once it is established that the project is a PHP project (PHP stack incomposer.json) and the change touches PHP code — skip it for non-PHP work (docs, tooling, infra, config); do not load the PHP standards for a task that does not touch PHP. - If the current project uses Laravel, also apply
@rules/laravel/laravel.mdc,@rules/laravel/architecture.mdc,@rules/laravel/filament.mdc, and@rules/laravel/livewire.mdc(likewise only when the change touches PHP) - Always follow this order: understand → propose → implement → verify
- Prefer existing project skills over custom solutions; do not duplicate logic already covered by a skill
Use when
- Solving a task that requires structured thinking and controlled execution
- Coordinating multiple steps or skills
Execution
1. Understand
- Analyze the problem, context, and related resources
- Classify the task (bug, feature, refactor, review, etc.)
- Define a short checklist of goals, constraints, and assumptions
2. Propose
- Suggest the smallest safe solution
- Explain why this approach is preferred (impact, risk, trade-offs)
- Select relevant existing skills to execute the plan
3. Implement
- Execute the solution using selected skills where applicable
- Keep changes focused and aligned with project conventions
- Add or update tests for changed behavior
4. Verify
- Validate the result against requirements
- Run relevant checks/tests for the affected scope
- Ensure no regressions or unintended side effects
- Summarize what was changed, tested, and any remaining risks
Done when
- The task is fully addressed
- The solution follows the defined loop
- Existing skills were reused where applicable
- Results are validated and clearly summarized
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 First seen · 47 lines · 26 tokens per session scan A 74b3d95fb4d7
understand-propose-implement-verify is a skill published in the GitHub repository pekral/cursor-rules (11 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 459 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
Laravel Dusk Testing
Expert-level Laravel Dusk browser testing skill for PHP/Laravel applications. Covers Chrome-based E2E testing, browser assertions, Page Objects, component testing, authentication helpers, and database integration.
laravel
Use when building or extending a Laravel 11/12 app — Eloquent models, migrations and relationships, routing with controllers and Form Requests, queues and background jobs, framework-native security (validation, mass-assignment, policies, signed URLs, rate limiting), and Pest/PHPUnit feature tests. NOT pure PHP…
owl-admin-app-dev
Use this skill when developing an application that installed slowlyo/owl-admin, especially backend CRUD, menus, permissions, controllers, services, routes, config/admin.php, app/Admin, helper functions, settings(), adminpages(), AdminPipeline, upload/file preview issues, route conflicts, custom login/menu examples, or…
owl-admin-devtools-generator
A development guide for Owl Admin, a Laravel-based administration system, covering its code generator, API templates, relationships, and visual pages.
owl-admin-amis-page
A reference skill for building Owl Admin pages with amis, a system for defining admin interfaces such as forms, tables, filters, and actions through schemas.