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/code-structuregit clone --depth 1 https://github.com/tbreeding/jira-mcpWhat 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
code-structure 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 yesterday.
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
Code Structure
- [MUST] No default exports, only named exports
- Organize by features/domains as top-level folders
- Write tests in adjacent tests folders.
- Use consistent folder structure within features
- Group related files in a single directory
- Limit file size to maintain readability (max ~80 lines)
- One component/module per file
- Separate business logic from side effects like API calls or UI rendering
- Keep configuration separate from implementation
- Avoid circular dependencies
- Minimize the visibility scope of functions and variables
- Consider organizing files by their role in the application (services, utils, controllers, etc.)
- Keep directory nesting to a minimum (max 3-4 levels deep)
- Types should be relegated to "types" subfolders located in adjacent folders to their production code
- Follow the naming pattern
*.type.tsfor type files - Interface names should not start with "I" prefix
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.
- yesterday First seen · 24 lines · 209 tokens per session scan A 20c12f8dbca3
code-structure 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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.