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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/core-development)<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/core-development"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/core-development.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.00561 | $0.00561 |
| Opus 5 | $0.00280 | $0.00280 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
core-development 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 7d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Development Rules
Code Quality Standards
ALWAYS
- Type safety — Use proper types. No
anyin TypeScript without explicit justification. Use type hints in Python. - Error handling — Handle all error paths explicitly. No empty catch blocks. No silent failures.
- Logging — Use the project's logging framework. Never use
console.logfor production code (uselogger.info,logger.error, etc.). - Configuration — Externalize all configuration values. No hardcoded API keys, URLs, ports, or magic numbers.
- Functions — Keep functions under 50 lines. Each function does ONE thing (Single Responsibility).
- Naming — Use descriptive, self-documenting names. Avoid abbreviations. Match existing codebase conventions.
- Comments — Comment the WHY, not the WHAT. Code should be self-explanatory for the "what."
- DRY — Don't Repeat Yourself. If you write the same logic twice, extract it.
NEVER
- Leave
console.logdebugging statements in production code - Use
anytype without a comment explaining why - Catch errors silently:
catch(e) {} - Hardcode values that should be configurable
- Skip input validation on user-facing endpoints
- Copy-paste code blocks (extract shared logic)
- Leave TODO/FIXME without an associated issue number
- Introduce new dependencies without justification
Architecture Principles (SOLID)
- Single Responsibility — Each class/module has one reason to change
- Open/Closed — Open for extension, closed for modification (use interfaces/abstract classes)
- Liskov Substitution — Subtypes must be substitutable for their base types
- Interface Segregation — Many specific interfaces over one general-purpose
- Dependency Inversion — Depend on abstractions, not concretions
Testing Requirements
- Every new feature needs tests covering happy path AND error paths
- Tests must be independent (no shared mutable state between tests)
- Test names describe the behavior:
should return empty array when no items match - Mock external dependencies, not internal logic
- Test coverage should not decrease with new changes
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.
- 7d ago First seen · 56 lines · 561 tokens per session scan A 6f8273002351
core-development is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 561 tokens to every session, about $0.0028 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-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.