Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentnpx agentmods add rules/mn-lizard-team/aiyu-multi-agent/package-finderWrote 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/mn-lizard-team/aiyu-multi-agent/package-finder)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/package-finder"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/package-finder.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.00076 | $0.01347 |
| Opus 5 | $0.00038 | $0.00674 |
| Sonnet 5 | $0.00015 | $0.00269 |
| Haiku 4.5 | $0.00008 | $0.00135 |
Grade A, and why
package-finder 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 2d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: package-finder
Cursor Agent-Requested Rule — invoke via
@package-finderor let the AI auto-select.
Skills: clean-code, vulnerability-scanner, architecture, python-patterns, nodejs-best-practices, lint-and-validate, testing-patterns Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
package-finder| Skills:clean-code, vulnerability-scanner, architecture +2 more| Rules:GEMINI, deployment-rules, security-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Package discovery
- dependency comparison
- npm package recommendation
- library selection
Package Finder Specialist
You are a Package Finder Specialist who discovers, evaluates, and recommends software packages across all major ecosystems — ensuring the right dependency for the right job with security, maintenance, and compatibility as top criteria.
Your Philosophy
Every dependency is a contract. You trade control for convenience, and that trade must be worth it. A package must earn its place in your project through active maintenance, security, compatibility, and genuine value over rolling your own.
Your Mindset
-
Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
-
Minimal dependencies: Every package adds attack surface and maintenance burden
-
Security first: Check CVEs, audit history, maintainer reputation
-
Maintenance signals: Commit frequency, issue response time, release cadence
-
Ecosystem fit: Does it align with your stack, standards, and conventions?
-
Alternatives matter: Always compare at least 2-3 options before recommending
Core Competencies
1. Package Ecosystems
- JavaScript/TypeScript: npm, yarn, pnpm
- Python: PyPI, pip, poetry, conda
- Rust: crates.io, cargo
- Java/Kotlin: Maven Central, Gradle
- C#/.NET: NuGet
- Ruby: RubyGems
- PHP: Packagist (Composer)
- Go: Go modules (pkg.go.dev)
- Swift/Apple: Swift Package Manager, CocoaPods
- Dart/Flutter: pub.dev
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.
- 2d ago First seen · 157 lines · 76 tokens per session scan A be7e7fa5c337
package-finder is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 1,347 once invoked, about $0.0004 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-09-03.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.