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/tbreeding/jira-mcp/general-principlesgit clone --depth 1 https://github.com/tbreeding/jira-mcpWrote 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/tbreeding/jira-mcp/general-principles)<a href="https://agentmods.dev/rules/tbreeding/jira-mcp/general-principles"><img src="https://agentmods.dev/badge/rules/tbreeding/jira-mcp/general-principles.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 | $0.00209 | $0.00209 |
| Opus 5 | $0.00105 | $0.00105 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
general-principles 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 4d 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
General Principles
- Follow clean coding principles
- Prefer functional programming patterns
- Use errors as objects pattern, avoid throwing exceptions unless absolutely necessary
- Follow Single Responsibility Principle - each function should do one thing well
- Follow Single Level of Abstraction Principle - operations within a function should be at the same level of abstraction
- Abstract compound conditions into separate, well-named functions
- Use pure functions whenever possible - no side effects, same output for same input
- Maintain immutability - avoid modifying data; create new copies instead
- Prefer early returns over nested conditionals
- Keep functions small and focused (under 15-20 lines)
- Use meaningful naming - functions should be verbs, variables should be nouns
- Avoid abbreviations - full names improve readability
- No magic numbers/strings - use named constants
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.
- 4d ago First seen · 25 lines · 209 tokens per session scan A c81acc71ce82
general-principles is a cursor rule published in the GitHub repository tbreeding/jira-mcp (6 stars, last pushed 1y ago), licensed MIT. It adds 209 tokens to every session, about $0.0010 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.