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/synmux/myriadWrote 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/synmux/myriad/packages-projects)<a href="https://agentmods.dev/rules/synmux/myriad/packages-projects"><img src="https://agentmods.dev/badge/rules/synmux/myriad/packages-projects/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/rules/synmux/myriad/packages-projects"><img src="https://agentmods.dev/badge/rules/synmux/myriad/packages-projects.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.00405 | $0.00405 |
| Opus 5.5 | $0.00162 | $0.00162 |
| Sonnet 5.5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
packages-projects 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
Package Managers
JavaScript/TypeScript
Use bun for package management. In package.json scripts, use bun run prefix.
If the package.json script cf-typegen exists, add types as an alias to it with bun run cf-typegen.
If this is a Cloudflare Worker or worker-configuration.d.ts exists, run bun types after any modifications to wrangler.jsonc or wrangler.toml (or any configuration change).
Python
Use uv for project initialization and management. Prefer manager-agnostic directives in package definitions; use uv-specific directives only when generic options aren't feasible.
- Run things with
uv run. If you have a command name created inpyproject.toml, you can douv run COMMANDNAME. - Update packages with
uv sync.
uv subcommands:
run: Run a command or scriptinit: Create a new projectadd: Add dependencies to the projectremove: Remove dependencies from the projectsync: Update the project's environmentlock: Update the project's lockfileexport: Export the project's lockfile to an alternate formattree: Display the project's dependency treetool: Run and install commands provided by Python packagespython: Manage Python versions and installationspip: Manage Python packages with a pip-compatible interfacevenv: Create a virtual environmentbuild: Build Python packages into source distributions and wheelspublish: Upload distributions to an indexcache: Manage uv's cacheself: Manage the uv executableversion: Read or update the project's versionhelp: Display documentation for a command
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 · 43 lines · 405 tokens per session scan A 510ad55e6dbe
packages-projects is a cursor rule published in the GitHub repository synmux/myriad (2 stars, last pushed today), licensed MIT. It adds 405 tokens to every session, about $0.0016 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-08-31.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).