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 rules/synmux/myriad/finalisegit clone --depth 1 https://github.com/synmux/myriadWhat 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.00492 | $0.00492 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
finalise 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standard Finalization Procedure
This document outlines the standard procedure to follow after making any changes to the codebase.
Testing
- Run the test suite to ensure all tests pass
mise test - If tests fail, fix the issues by either:
- Updating the code to match the test expectations
- Updating the tests to match the new code behavior (if the changes were intentional)
- Remember that the codebase requires Python 3.13+
Code Quality Checks
- Run Trunk checks to identify and fix issues:
trunk check -a --show-existing - Use the
--show-existingflag to see all issues, including those that might be ignored by default - For targeted checks on specific files:
trunk check --show-existing FILENAME - Fix issues using appropriate methods:
- For formatting issues:
trunk fmt FILENAMEortrunk fmt -a - For linting issues: attempt fix with
trunk check --fix FILENAMEortrunk check --fix -a
- For formatting issues:
Documentation Updates
After any feature changes or additions, update the following documentation files:
- README.md: User-facing documentation with usage examples
- CLAUDE.md: Detailed information for AI assistants to understand the codebase
- PROMPT.md: Analysis of the implementation and prompt guidance
Ensure that all three files remain in sync and provide accurate information about the project structure, features, and usage.
Sample Directory Management
The sample directory is used for testing purposes and can be reset to its original state using:
mise reset
When making changes to the sample files:
- Update the
.sample-sourcedirectory first - Then run the reset script to propagate those changes to the
sampledirectory - This ensures that users can easily reset to a clean state for testing
Final Verification
Before considering a change complete:
- Verify all tests pass
- Confirm all Trunk checks pass
- Ensure documentation is updated
- Check that the sample files are working as expected
- Manually test the affected functionality
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 · 70 lines · 492 tokens per session scan A 1cf378f22c6a
finalise is a cursor rule published in the GitHub repository synmux/myriad (2 stars, last pushed 2d ago), licensed MIT. It adds 492 tokens to every session, about $0.0025 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 cursor rules, from other repositories
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.