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 smartest-project-additiongit 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/smartest-project-addition)<a href="https://agentmods.dev/skills/pekral/cursor-rules/smartest-project-addition"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/smartest-project-addition/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/smartest-project-addition"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/smartest-project-addition.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.00023 | $0.00333 |
| Opus 5.5 | $0.00009 | $0.00133 |
| Sonnet 5.5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
smartest-project-addition 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 proposed addition touches PHP code — skip it for a non-PHP project or a non-code proposal; do not load the PHP standards when the addition does not touch PHP. - Recommend exactly one addition
- Do not include alternative proposals in the final answer
- Do not implement code unless explicitly requested
Use when
- You want the single most valuable next addition to the project
- You want a concrete recommendation, not a list of ideas
Required approach
- Inspect the current repository and identify the strongest leverage point across architecture, DX, reliability, performance, security, or delivery speed
- Evaluate candidate ideas by:
- impact
- implementation complexity
- risk
- reversibility
- Select exactly one proposal with the best overall leverage
Output
Provide:
- a concise proposal statement
- why this is the best next addition now
- expected business and technical benefits
- key risks and mitigations
- smallest safe implementation plan
- test/validation strategy
- rollout and rollback notes
Done when
- The recommendation is concrete, measurable, and actionable
- The final answer contains exactly one proposal
- The proposal is justified by impact relative to complexity and risk
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 · 42 lines · 23 tokens per session scan A 473e9a97e828
smartest-project-addition is a skill published in the GitHub repository pekral/cursor-rules (11 stars, last pushed 19d ago), licensed MIT. It adds 23 tokens to every session and 333 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
ponytail-debt
Harvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.