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/permitio/permit-fastmcp/basicgit clone --depth 1 https://github.com/permitio/permit-fastmcpWhat 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.00000 | $0.00304 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
basic 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.
What it actually says
CursorRules for permit-fastmcp
Python Best Practices
- Follow PEP8 for code style and formatting.
- Use type hints and docstrings for all public functions and classes.
- Prefer async/await for I/O-bound operations.
- Use logging instead of print statements.
- Handle exceptions gracefully and provide helpful error messages.
- Keep functions small and focused; prefer composition over inheritance.
- Use environment variables or config files for secrets and settings.
- Write tests for new features and bug fixes.
Attitude
When a soild fix - apply it without asking
Dependency Management & Publishing
- Use
uvfor installing, updating, and publishing packages:- Install dependencies:
uv pip install -r requirements.txt - Add a dependency:
uv pip install <package> - Update lockfile:
uv pip compile - Publish:
uv publish
- Install dependencies:
- Keep
requirements.txt,pyproject.toml, anduv.lockin sync.
Documentation & Project Hygiene
- Update
llms.txtwith any new usage patterns, configuration, or developer instructions. - Update
README.mdto reflect new features, configuration options, or breaking changes. - Add or update inline comments for complex logic.
- Ensure all public APIs are documented.
General
- Use descriptive commit messages.
- Remove unused code and files.
- Keep the codebase clean and organized.
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 · 38 lines · 0 tokens per session scan A 065dcb15687a
basic is a cursor rule published in the GitHub repository permitio/permit-fastmcp (17 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 304 tokens. 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-30.
Other cursor rules, from other repositories
architecture-rules
Cursor rule "architecture-rules" from theronic/eacl, covering understanding, service boundaries, api design, event-driven architecture and datastore guidelines.
deployment-rules
Cursor rule "deployment-rules" from theronic/eacl, covering preparation, infrastructure as code, ci/cd integration, strategies and observability.
documentation-rules
Cursor rule "documentation-rules" from theronic/eacl, covering generation, api documentation, code documentation, operational docs and african market context.
security-rules
Cursor rule "security-rules" from theronic/eacl, covering awareness, code generation, authentication & authorization, data protection and infrastructure security.
testing-rules
Cursor rule "testing-rules" from theronic/eacl, covering generation principles, test types, quality guidelines, modifications and african context.
verification-rules
Cursor rule "verification-rules" from theronic/eacl, covering first principles, methods, test-driven development, coverage requirements and african context.