Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/mordilion/ai-instructions-and-prompts/general)<a href="https://agentmods.dev/rules/mordilion/ai-instructions-and-prompts/general"><img src="https://agentmods.dev/badge/rules/mordilion/ai-instructions-and-prompts/general/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/mordilion/ai-instructions-and-prompts/general"><img src="https://agentmods.dev/badge/rules/mordilion/ai-instructions-and-prompts/general.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.01634 | $0.01634 |
| Opus 5 | $0.00817 | $0.00817 |
| Sonnet 5 | $0.00327 | $0.00327 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
general 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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Instructions & Prompts (Claude Code Plugin)
Scope: This applies to ALL tasks. Always active.
Project Nature: This is a meta-project that creates a Claude Code plugin providing AI rules, processes, and prompts for end users.
Project Goals:
- Users install the plugin and run
/ai-iap:setupto configure Claude Code rules for their projects - Provide rules and processes as modular Claude Code rules (
.claude/rules/**/*.md) - All files for rules and processes MUST be token efficient and clear
- NEVER work with fixed versions. Use user's project-related versions and make it flexible
- Files MUST follow the same structure for better maintainability
Plugin Structure (this repository; all under plugin/ except marketplace root):
plugin/.claude-plugin/plugin.json— Plugin manifestplugin/skills/setup/SKILL.md— Interactive setup wizard (/ai-iap:setup)plugin/skills/validate/SKILL.md— Configuration validator (/ai-iap:validate)plugin/agents/*.md— Built-in agents (code-reviewer, codebase-explorer, test-writer, docs-writer, refactor-helper)plugin/hooks/hooks.json— SessionStart hook for setup hintplugin/lib/config.json— Central configuration (languages, frameworks, structures, processes)plugin/lib/config.schema.json— JSON schema for config validationplugin/lib/claude-subagents.json— Agent templates with rule bindingsplugin/lib/rules/— Rule library (general → language → framework → structure)plugin/lib/processes/— Process guides (testing, CI/CD, logging, docker, auth, etc.)plugin/lib/code-library/— Implementation patterns + design patterns
Success Criteria:
- Consistent code structure and architecture patterns
- Same security practices applied (OWASP Top 10, input validation, etc.)
- Same testing approaches (unit, integration, mocking)
- Same CI/CD best practices (version detection, caching, matrix testing)
CRITICAL RULE - Check Functions BEFORE Generating Code
BEFORE implementing error handling, async operations, input validation, database queries, HTTP requests, or other covered function patterns:
- CHECK the functions index — same file, two valid path roots: from this Git repo
plugin/lib/code-library/functions/INDEX.md; from the installed plugin directory (CLAUDE_PLUGIN_ROOT, thepluginfolder)lib/code-library/functions/INDEX.md- USE the exact pattern from the function file (e.g.,
error-handling.md)- CHOOSE the appropriate framework version (Plain, Prisma, Laravel, etc.)
- COPY the exact code pattern (no installation commands)
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.
- 9d ago First seen · 123 lines · 1,634 tokens per session scan A 1fb9b7b906e7
general is a cursor rule published in the GitHub repository mordilion/ai-instructions-and-prompts (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,634 tokens to every session, about $0.0082 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
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.